coderabbit-deploy-integration

Roll out CodeRabbit across an organization: multi-repo deployment, org-level config, and team onboarding. Use when deploying CodeRabbit org-wide, creating shared configurations, or onboarding development teams to AI code review. Trigger with phrases like "deploy coderabbit", "coderabbit org rollout", "coderabbit multi-repo", "coderabbit onboarding", "coderabbit team setup".

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%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.

Strong, actionable skill body with executable configs and scripts organized into a clear phased rollout. The main gap is the absence of per-repo validation checkpoints in the batch deployment and branch-protection loops, which leaves error recovery implicit.

Suggestions

Add a validation checkpoint inside the deploy-coderabbit-config.sh loop (e.g., check `gh pr create` exit status and confirm the PR URL before proceeding to the next repo) so a failure in one repo is surfaced immediately.

After Step 5's branch-protection loop, add a verification step (e.g., `gh api repos/$ORG/$REPO/branches/main/protection` GET) confirming the protection rule and required 'coderabbitai' context are actually active.

Add an explicit feedback loop in the Error Handling section: when a repo config is ignored, instruct re-running `@coderabbitai configuration` to confirm the new config is active before moving on.

Dimension	Reasoning	Score
Conciseness	Lean and token-efficient — directly presents executable YAML configs and bash scripts with minimal conceptual padding, assuming Claude's competence rather than explaining basics.	3 / 3
Actionability	Provides fully executable, copy-paste-ready content: complete .coderabbit.yaml configs, a working deploy loop using gh/git, and branch-protection gh api calls with concrete parameters.	3 / 3
Workflow Clarity	A clear six-step phased sequence exists, but the batch multi-repo deployment script and branch-protection loop run without any validation checkpoint verifying each repo succeeded before proceeding — the rubric caps batch operations lacking validation at 2.	2 / 3
Progressive Disclosure	Well-organized into clear sections in a single self-contained file, with only one-level-deep external links (CodeRabbit docs and a sibling skill) and no nested reference chains; no bundle files exist to misorganize.	3 / 3
	Total	11 / 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 well-crafted description that clearly states capabilities, gives explicit 'Use when' guidance, and includes natural trigger phrases with a distinct, low-conflict niche. No significant weaknesses.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'multi-repo deployment, org-level config, and team onboarding' — matching the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (roll out CodeRabbit org-wide) and when via a 'Use when...' clause plus explicit trigger phrases, satisfying the highest completeness anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would actually say ('deploy coderabbit', 'coderabbit org rollout', 'coderabbit onboarding', 'coderabbit team setup'), giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Targeted CodeRabbit-org-deployment niche with distinct 'coderabbit' triggers makes it 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
Path: plugins/saas-packs/coderabbit-pack/skills/coderabbit-deploy-integration/SKILL.md
Commit: 4c47e33

Reviewed: 3 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.