coderabbit-core-workflow-a

Execute CodeRabbit primary workflow: automated PR code review with configuration. Use when setting up automated code reviews on pull requests, configuring review behavior, or establishing the core CodeRabbit review loop. Trigger with phrases like "coderabbit review workflow", "coderabbit PR review", "coderabbit auto review", "configure coderabbit reviews".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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 config and commands and a clear lifecycle, but it is a single monolithic file where detail-heavy content (full config, recipes) could be offloaded to reference files, and the workflow lacks explicit validation checkpoints.

Suggestions

Move the full production .coderabbit.yaml reference and finishing-touch recipes into reference files (e.g., references/configuration.md, references/recipes.md) and keep SKILL.md as a concise overview with one-level-deep links.

Add an explicit validation step to the workflow, e.g. run '@coderabbitai configuration' to confirm the parsed config before expecting reviews, with a fix-and-retry loop.

Trim the extensive inline YAML comments or collapse the two separate reviews blocks (the second redeclares 'reviews:' and could merge with the first) to reduce token weight.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of concepts Claude already knows, but the large production-ready YAML block with extensive inline comments and the separate recipe block add weight that could be trimmed or moved to a reference for an overview skill.	2 / 3
Actionability	Provides fully executable, copy-paste-ready YAML configuration, concrete @coderabbitai commands, and specific recipe examples — no pseudocode or vague direction.	3 / 3
Workflow Clarity	The four-step sequence and lifecycle diagram give a clear flow, but there are no embedded validation checkpoints (e.g., verify config before relying on a review); error recovery lives in a separate table rather than as validate-then-proceed steps.	2 / 3
Progressive Disclosure	Sections are well-organized and external doc links plus sibling skills are signaled, but no bundle files exist and the full config reference, lifecycle, and recipes are all inlined in SKILL.md rather than split into one-level-deep references.	2 / 3
	Total	9 / 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.

The description is third-person, concise, and clearly states both the capability and the triggering conditions with concrete, natural phrases. It is well-scoped to CodeRabbit and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'automated PR code review with configuration', 'setting up automated code reviews on pull requests', 'configuring review behavior', 'establishing the core CodeRabbit review loop' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Execute CodeRabbit primary workflow: automated PR code review with configuration') and when ('Use when setting up automated code reviews...') with explicit triggers, satisfying the highest anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would say ('coderabbit review workflow', 'coderabbit PR review', 'coderabbit auto review', 'configure coderabbit reviews') alongside a 'Use when' clause, giving good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	Scoped to a named product (CodeRabbit) with product-specific trigger phrases, making it clearly distinguishable and unlikely to fire for unrelated review 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: 3022dd3

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.