coderabbit-multi-env-setup

Configure CodeRabbit review behavior per branch and environment using path instructions and base branches. Use when setting different review profiles per branch, configuring stricter reviews for release branches, or customizing CodeRabbit behavior across dev/staging/prod workflows. Trigger with phrases like "coderabbit environments", "coderabbit staging", "coderabbit per-branch config", "coderabbit release review", "coderabbit environment setup".

Quality

82%

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

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

The body is highly actionable with executable configs and scripts and a clear step sequence, but it is verbose due to repetitive YAML blocks and lacks validation checkpoints around its destructive branch-sync and branch-protection operations. Progressive disclosure is limited since everything lives inline with no bundle files.

Suggestions

Factor the repeated YAML structure (language, auto_review, path_filters) into a shared base config and show only the per-branch diffs to cut token cost.

Add explicit validation/feedback loops to Step 4 and Step 6 — e.g., verify branch protection applied with `gh api .../branches/main/protection` and confirm configs landed via `git show` before declaring success.

Move the full per-branch .coderabbit.yaml examples into reference files under references/ and keep SKILL.md as an overview with one-level-deep links.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable configs and scripts, but ~270 lines include near-duplicate YAML blocks (each branch config repeats language, auto_review, path_filters) that could be tightened or factored. Not score 3 because the repetition and some restated context add tokens that don't each earn their place; not score 1 because it largely avoids explaining concepts Claude already knows.	2 / 3
Actionability	Provides fully executable copy-paste-ready YAML configs, a complete bash sync script, concrete `gh api` branch-protection commands, and verification snippets. Not score 2 because the guidance is concrete and complete rather than pseudocode or abstract direction.	3 / 3
Workflow Clarity	Steps are sequenced (Step 1–6) with a verification step (Step 5: `@coderabbitai configuration`, `git show main:.coderabbit.yaml`), but the destructive/batch operations in Step 4 (git checkout/commit across branches) and Step 6 (branch protection PUT) lack explicit validation checkpoints or feedback loops. Per the rubric, missing validation for destructive/batch ops caps workflow clarity at 2; not score 1 because the sequence is present and one verification step exists.	2 / 3
Progressive Disclosure	Single SKILL.md with no bundle files present (references/, scripts/, assets/ all empty), so all full configs are inline rather than split into separate files; navigation is limited to one sibling-skill pointer at the end. Not score 3 because large config blocks that could be separate files are inline; not score 1 because sections are clearly organized and references are one level deep.	2 / 3
	Total	9 / 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 description that clearly states concrete capabilities, explicit use-when triggers, and natural trigger phrases in third-person voice. It fully answers both what the skill does and when to invoke it without vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: 'Configure CodeRabbit review behavior per branch and environment using path instructions and base branches', 'setting different review profiles per branch', 'configuring stricter reviews for release branches', and 'customizing CodeRabbit behavior across dev/staging/prod workflows'. Not score 2 because it goes beyond naming a domain to enumerate several specific concrete actions.	3 / 3
Completeness	Clearly answers both what ('Configure CodeRabbit review behavior per branch and environment') and when ('Use when setting different review profiles per branch, configuring stricter reviews for release branches, or customizing CodeRabbit behavior across dev/staging/prod workflows') with explicit triggers. Not score 2 because the 'Use when...' clause is explicit and complete.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would actually say: 'coderabbit environments', 'coderabbit staging', 'coderabbit per-branch config', 'coderabbit release review', 'coderabbit environment setup'. Not score 2 because coverage spans multiple natural phrasings rather than a single keyword.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (CodeRabbit per-branch/per-environment configuration) with distinct triggers unlikely to fire for unrelated skills. Not score 2 because the domain and triggers are specific enough to avoid overlap with generic review or CI 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-multi-env-setup/SKILL.md
Commit: 4c47e33

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