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

83%

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

92%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 lean, well-sequenced review playbook with explicit validation gates, conditional smoke-test loading, feedback loops, and a closing readiness checklist. Its only notable gap is the absence of illustrative examples for the more qualitative review dimensions.

DimensionReasoningScore

Conciseness

The body is dense imperative guidance with zero padding — no explanation of what code review is, e.g. "Check domain fit: branch growth, synchronized flags, repeated shape assumptions, temporal decomposition, and missing state models" — every line adds non-obvious instruction, matching the lean anchor 5.

5 / 5

Actionability

Concrete copy-paste commands are present ("npx ai-devkit@latest lint", "git status -sb", "git diff --stat") and most steps are executable directives, but qualitative checks like boundary discipline and domain fit lack any illustrative example of a violation, matching anchor 4 rather than fully-executable anchor 5.

4 / 5

Workflow Clarity

The sequence is explicit and numbered with validation gates ("Run npx ai-devkit@latest lint before phase work", "Load verify ... before claiming readiness", conditional dev-smoke with a stated-reason requirement), a feedback loop ("If blocking issues remain, return to dev-implementation or dev-testing"), and a final checklist — matching anchor 5's validation-plus-feedback-loop pattern.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files and no content that warrants external references; sections (Phase Contract, Code Review, Done) are well-organized and cross-skill loads (verify, dev-smoke, task) are clearly signaled, satisfying the rubric's simple-skill criterion for a 5.

5 / 5

Total

19

/

20

Passed

Description

66%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 a clear explicit trigger clause and acceptable domain framing, but the capability statement is thin on concrete actions and the generic "code review" trigger creates conflict risk with broader code-review skills. It reads as an ecosystem-internal phase pointer more than a self-contained skill description.

Suggestions

State 2-3 concrete actions the skill performs, e.g. "Runs holistic pre-push review: verifies design alignment, traces callers of modified exports, checks contract integrity, and emits severity-ordered findings with file/line references."

Add natural trigger variations users would actually say, such as "review my changes/diff", "pre-push review", or "PR readiness check", alongside the existing phase-9 triggers.

Reduce conflict risk with generic code-review skills by making the primary trigger the more distinctive phrases ("final lifecycle review", "dev-lifecycle phase 9") and qualifying plain "code review" with the AI DevKit / pre-push context.

DimensionReasoningScore

Specificity

"Final code review phase guidance for holistic pre-push review" names the domain and only 1-2 actions; it never states concrete review activities like producing severity-ordered findings or tracing callers, so it matches anchor 3 rather than the several-specific-actions anchor 4.

3 / 5

Completeness

Both parts are present: a "what" ("Final code review phase guidance for holistic pre-push review") and an explicit "Use when..." clause with concrete triggers, but the "what" is phrased as "guidance for" rather than clearly stating what the skill does, matching anchor 4 instead of the crisp anchor 5.

4 / 5

Trigger Term Quality

"Use when the user wants code review" captures the dominant natural phrase, and "design alignment checks" and "integration risk review" add coverage, but common variations users actually say ("review my diff/changes", "PR review") are missing, matching anchor 4 rather than comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Use when the user wants code review" creates real overlap with any general code-review skill, though the "AI DevKit" branding and "dev-lifecycle phase 9" qualifier narrow the niche, placing it at anchor 3 rather than the mostly-distinct anchor 4.

3 / 5

Total

14

/

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.