code-review

Review a diff for proven defects. Trigger: review this PR/branch/diff, code review, pre-merge check.

Quality

87%

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

88%Weight 40%Scale 1-5

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

A tight, well-structured review procedure with concrete commands, explicit per-step completion checkpoints, and a verification feedback loop. The main blemish is a broken reference to references/workflows.md and prose-only (rather than literal code) guidance.

Suggestions

Fix or remove the broken reference: the intro cites references/workflows.md → "Code review a PR", but no workflows.md exists in the bundle.

For the report step, include a one-line literal output template (e.g. `**{what}** — {file:line} — {scenario} — {fix}`) to move actionability from prose direction to copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — no padding, no explaining what a diff or git is, every line earning its place — matching the score-5 anchor.	5 / 5
Actionability	Concrete commands (git diff, gh pr diff, ado pr diff) and a precise one-line output format make the guidance executable, but it is prose direction rather than copy-paste code blocks, so it sits at 4 rather than 5.	4 / 5
Workflow Clarity	Five sequenced steps (Scope, Trace, Hunt, Verify, Report) each with an explicit "Done when" checkpoint, and step 4 is a verify/feedback loop that confirms or downgrades blocking findings — matching the score-5 anchor.	5 / 5
Progressive Disclosure	The overview points one level deep to clearly signaled references (lenses.md, findings.md) that both exist, but the intro also references references/workflows.md which is not present in the bundle, so organization is good with a minor gap keeping it at 4.	4 / 5
	Total	18 / 20 Passed

Description

86%Weight 40%Scale 1-5

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 concise, third-person description with an explicit and comprehensive trigger clause that clearly answers both what and when. Its only weakness is that the capability side names a single broad action rather than enumerating several specific ones.

Suggestions

List 1-2 more concrete capabilities (e.g. ranks findings by severity, writes file:line failure scenarios) to lift specificity from 3 toward 4-5.

Add a distinguishing phrase (e.g. "proven defects only — not preferences or nits") to further separate it from a general /review skill and reduce overlap risk.

Dimension	Reasoning	Score
Specificity	"Review a diff for proven defects" names the domain and one concrete action but does not list multiple specific actions, matching the score-3 anchor; it stops short of the several-actions coverage expected for a 4.	3 / 5
Completeness	It states what ("Review a diff for proven defects") and when (the Trigger clause with concrete phrases), explicitly answering both per the score-5 anchor.	5 / 5
Trigger Term Quality	The explicit "Trigger: review this PR/branch/diff, code review, pre-merge check" provides comprehensive natural terms and synonyms a user would actually say, matching the score-5 anchor.	5 / 5
Distinctiveness Conflict Risk	The diff/proven-defects framing carves a mostly distinct niche, but "code review" / "review this PR" overlap broadly with a general review skill, so minor overlap risk keeps it at 4 rather than 5.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: YoizenSA/dev-ai-workflow
Path: ywai/skills/code-review/SKILL.md
Commit: 36f5af5

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.