coderabbit-ci-integration

Configure CodeRabbit as a CI gate with GitHub Actions, branch protection, and review enforcement. Use when setting up CodeRabbit as a required check, gating merges on review approval, or integrating CodeRabbit status into your CI pipeline. Trigger with phrases like "coderabbit CI", "coderabbit GitHub Actions", "coderabbit required check", "coderabbit merge gate", "coderabbit CI pipeline".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An actionable, mostly lean skill body built around executable code, but it keeps all six workflows in a single inline file and lacks explicit verification checkpoints between steps. Splitting workflows into referenced files and adding validate-after-each-step feedback would raise the weaker dimensions.

Suggestions

Add inline verification checkpoints (e.g., after Step 1 confirm 'coderabbitai' appears in the required checks list; after the branch-protection PUT run `gh api .../protection` to confirm the context is required) to turn the sequence into a validate→fix→retry loop.

Move the larger workflow examples (pr-size-check, coderabbit-notify, branch-protection API) into reference files under references/ and link to them from SKILL.md, keeping the body a concise overview with one-level-deep navigation.

Trim the reactive Error Handling table or fold each cause/solution into its relevant step so recovery guidance sits next to the action that can fail.

Dimension	Reasoning	Score
Conciseness	The body is code-dense and lean; explanatory comments are tied to CodeRabbit-specific config keys and review states Claude would not already know, with little padding about general concepts.	3 / 3
Actionability	Provides fully executable YAML workflows, a copy-paste gh api branch-protection script, and numbered UI steps — concrete and ready to apply rather than abstract direction.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced, but there are no inline validation/verification checkpoints (e.g., confirm the check appears after enabling it, verify protection after the API PUT); the Error Handling table is reactive rather than a validate→fix→retry loop.	2 / 3
Progressive Disclosure	All six distinct workflows live inline in a ~210-line monolith with no references/scripts/assets bundle; sections are well organized, but content that could be split into one-level-deep reference files is not.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that concisely states concrete capabilities, gives an explicit Use-when clause, and supplies multiple natural trigger phrases. It is clearly distinguishable and avoids fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Configure CodeRabbit as a CI gate with GitHub Actions, branch protection, and review enforcement" — naming the specific mechanisms involved rather than vague capability claims.	3 / 3
Completeness	Explicitly answers both what (configure as CI gate with branch protection/review enforcement) and when ("Use when setting up CodeRabbit as a required check, gating merges on review approval, or integrating CodeRabbit status into your CI pipeline").	3 / 3
Trigger Term Quality	Provides natural phrases users would say — "coderabbit CI", "coderabbit GitHub Actions", "coderabbit required check", "coderabbit merge gate", "coderabbit CI pipeline" — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (CodeRabbit-specific CI gating) with distinct, product-named triggers unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 6e3a65f

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.