CtrlK
BlogDocsLog inGet started
Tessl Logo

coderabbit-prod-checklist

Execute CodeRabbit production readiness checklist for org-wide deployment. Use when preparing to enforce CodeRabbit reviews, going live with required checks, or auditing CodeRabbit configuration before making it a merge gate. Trigger with phrases like "coderabbit production", "coderabbit go-live", "coderabbit launch checklist", "coderabbit readiness", "coderabbit pre-launch".

76

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

92%

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

A highly actionable, well-sequenced production-readiness checklist with executable code, validation, and monitoring. The main weakness is monolithic inline content that could benefit from splitting dense templates and checklists into reference files.

Suggestions

Move the full production .coderabbit.yaml template (Step 6) into a references/ file and link to it, keeping only key field highlights inline in SKILL.md.

Extract the markdown checklists (Steps 1, 4, 7) into a references/checklist.md so the main body stays a lean overview pointing to one-level-deep materials.

Add a verification step after the Step 5 branch-protection PUT (e.g., re-fetch protection rules) to confirm the required check was actually applied before declaring success.

DimensionReasoningScore

Conciseness

Lean content with no concept-explanation fluff (no 'what is CodeRabbit' padding); nearly every token is an executable checklist item, bash snippet, or config block that earns its place.

3 / 3

Actionability

Provides fully executable bash (gh api calls, Python YAML validation), a complete production .coderabbit.yaml template, and copy-paste-ready checklists throughout all seven steps.

3 / 3

Workflow Clarity

Seven explicitly sequenced steps with validation checkpoints (Step 2 validates config, Step 3 verifies coverage) and a post-launch monitoring plus error-handling table providing feedback loops for the risky production cutover.

3 / 3

Progressive Disclosure

Well-organized into clear sections, but it is a single monolithic ~250-line SKILL.md with no bundle files; the large YAML template and multiple inline markdown checklists could be split into one-level-deep reference files for easier navigation.

2 / 3

Total

11

/

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 tight, third-person description that covers concrete actions, explicit trigger guidance, and a distinct niche with no conflict risk. Both the 'what' and 'when' are explicit.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Execute CodeRabbit production readiness checklist', 'preparing to enforce CodeRabbit reviews', 'going live with required checks', 'auditing CodeRabbit configuration' — rather than vague language.

3 / 3

Completeness

Clearly states both what it does (execute the production readiness checklist for org-wide deployment) and when to use it via an explicit 'Use when...' clause with concrete scenarios.

3 / 3

Trigger Term Quality

Explicit natural trigger phrases are provided — 'coderabbit production', 'coderabbit go-live', 'coderabbit launch checklist', 'coderabbit readiness', 'coderabbit pre-launch' — covering terms a user would realistically say.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (CodeRabbit production merge-gate deployment) with distinct, brand-specific triggers unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.