CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dev-review

AI DevKit · Final code review phase guidance for holistic pre-push review. Use when the user wants code review, final lifecycle review, design alignment checks, integration risk review, or dev-lifecycle phase 9.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a compact, well-sequenced review workflow with explicit validation checkpoints, a blocker-driven feedback loop, and a final readiness checklist; it stays lean and assumes Claude's competence, with only minor redundancy across the checklist steps.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no explanations of concepts Claude already knows, but steps 13-14 and the step 17 checklist partially repeat checks already covered in steps 5-12, so minor trimming is possible.

4 / 5

Actionability

Concrete commands are given ("npx ai-devkit@latest lint", "git status -sb", "git diff --stat") plus specific directives like "grep exported names to trace callers and dependents"; as an instruction-only skill the guidance is executable, with only minor gaps such as no example finding format for step 15.

4 / 5

Workflow Clarity

The sequence is clear with explicit validation gates ("Apply the `verify` skill before claiming readiness. Run `dev-smoke`..."), an error-recovery feedback loop ("If blocking issues remain, return to `dev-implementation` or `dev-testing`"), and a final completion checklist, matching the top anchor.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references, and its sections (Phase Contract, Code Review, Done) are well organized with clearly signaled cross-skill references (`verify`, `dev-smoke`, `task`), satisfying the simple-skill exception for a top score.

5 / 5

Total

18

/

20

Passed

Description

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

The description has an exemplary explicit trigger clause with concrete use-cases and good keyword coverage, but the capability statement is an indirect noun-phrase label with mild buzzword padding, and the generic "code review" trigger creates real overlap risk with general review skills.

Suggestions

State the what as a direct third-person action (e.g., "Performs the final holistic pre-push code review for AI DevKit features...") instead of the noun-phrase label "Final code review phase guidance".

Qualify the generic "code review" trigger to reduce conflict with general review skills, e.g., "Use when the user wants the final pre-push review of an AI DevKit feature (dev-lifecycle phase 9)...".

Add one or two natural user phrasings such as "final review before pushing" or "review changes before PR" to strengthen trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete review activities ("code review, final lifecycle review, design alignment checks, integration risk review"), matching the several-specific-actions anchor; falls short of 5 because "holistic pre-push review" is mildly fluffy and coverage of what the review produces is not stated.

4 / 5

Completeness

Both what and when are present and the "Use when..." clause is explicit with concrete triggers, but the what is an indirect noun phrase ("Final code review phase guidance for holistic pre-push review") rather than a direct statement of the action performed, placing it between the 4 and 5 anchors.

4 / 5

Trigger Term Quality

"code review" and "pre-push" are natural user phrases and multiple relevant keywords are present, but common variations like "review my changes", "PR review", or "final check before pushing" are missing, keeping it below the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

The generic "code review" trigger would compete with virtually any general code-review skill, so despite the distinctive "dev-lifecycle phase 9" niche markers, it sits at the somewhat-specific-but-overlapping anchor rather than mostly-distinct.

3 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

codeaholicguy/ai-devkit

Path

skills/dev-review/SKILL.md

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.