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

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

80%Weight 40%Scale 1-3

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

A highly actionable, concise CI integration skill with copy-paste-ready configs throughout. Its main weaknesses are the absence of validation checkpoints in the step sequence (notably around the destructive branch-protection step) and the lack of progressive disclosure — everything is inlined rather than split into reference files.

Suggestions

Add an explicit verification checkpoint after Step 1 (e.g. confirm 'coderabbitai' now appears as a required check) and a dry-run/test-PR validation before applying the Step 6 branch-protection change with enforce_admins=true.

Move the more ancillary workflows (PR size check, Slack notification) into a reference file under references/ and link to it from SKILL.md, keeping the core merge-gate flow inline for better progressive disclosure.

Add a brief 'verify the gate works' step that creates or uses a test PR to confirm CodeRabbit blocks merge on 'Changes Requested' before relying on the configuration.

Dimension	Reasoning	Score
Conciseness	The body is dense with actionable config (full workflows, YAML, gh API calls) and an error-handling table, with no padding explaining what GitHub Actions or branch protection are; inline YAML comments document config options rather than basic concepts.	3 / 3
Actionability	Every step ships complete, copy-paste-ready artifacts — full .coderabbit.yaml, three GitHub Actions workflow files, and a complete gh api branch-protection command — meeting the score-3 bar for executable, specific guidance.	3 / 3
Workflow Clarity	Steps 1–6 are clearly sequenced and the error-handling table gives recovery paths, but there are no explicit validate-before-proceeding checkpoints between steps, and the destructive Step 6 branch-protection call (enforce_admins=true) is applied with no verification, which caps clarity at 2.	2 / 3
Progressive Disclosure	Content is well-organized into labeled sections, but all six complete workflow files are inlined in SKILL.md with no bundle files (references/scripts/assets absent); several workflows (e.g. pr-size-check, notify) could live in one-level-deep reference files, so it sits at the 'some structure, content that should be separate is inline' anchor.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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, well-formed description: concrete actions, explicit 'Use when' guidance, natural trigger phrases, and a distinct niche. The incidental 'your CI pipeline' is a mild second-person touch but the voice is otherwise third-person imperative, so it does not warrant a specificity penalty.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Configure CodeRabbit as a CI gate with GitHub Actions, branch protection, and review enforcement' — matching the score-3 anchor of several specific actions rather than vague language.	3 / 3
Completeness	Explicitly states both what it does (configure CI gate, branch protection, review enforcement) and when to use it ('Use when setting up CodeRabbit as a required check, gating merges on review approval, or integrating CodeRabbit status into your CI pipeline'), with explicit triggers.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would say ('coderabbit CI', 'coderabbit GitHub Actions', 'coderabbit required check', 'coderabbit merge gate', 'coderabbit CI pipeline'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear CodeRabbit-specific niche with all triggers prefixed 'coderabbit', making it unlikely to fire for an unrelated skill.	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
Path: plugins/saas-packs/coderabbit-pack/skills/coderabbit-ci-integration/SKILL.md
Commit: 4c47e33

Reviewed: 1 day 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.