CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aif-review

Perform code review on staged changes or a pull request. Checks for bugs, security issues, performance problems, and best practices. Use when user says "review code", "check my code", "review PR", or "is this code okay". The +check flag validates findings via a fresh-context subagent; validation also runs automatically when the review produced confidence markers.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

73%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 highly actionable, well-sequenced review workflow with copy-paste commands, explicit validation checkpoints, and a real, well-signaled one-level reference bundle. Its main weakness is token efficiency: the marker-resolution and gate contract is duplicated across multiple body sections instead of being delegated once to the existing CHECK-MODE.md reference.

Suggestions

Collapse the duplicated marker/gate contract ('Machine-readable gate result', 'Resolving markers before the gate', and the Output Format validation notes) into a single short summary plus one pointer to references/CHECK-MODE.md, which already owns the full procedure.

Move the generic 'Runtime-aware questions' and 'Shared project skill-context' sections into a shared project-context reference or the skill-context layer, keeping the body focused on the review workflow itself.

Trim rationale prose (e.g. the 'Why: Opus 4.8…' note and 'The dispatch is paid only in runs that…' paragraph) or relocate it to the relevant reference file; the body needs the rule, not the design history.

DimensionReasoningScore

Conciseness

The ~430-line body restates the marker/validation/gate contract across at least three sections ("Behavior", "Machine-readable gate result", "Resolving markers before the gate", and the Output Format notes), and inlines generic harness-contract text ("Runtime-aware questions", "Shared project skill-context") plus rationale prose ("The dispatch is paid only in runs that…") that belongs in references/CHECK-MODE.md — noticeably verbose with several padded/duplicated sections, below the 'mostly efficient' bar of 3.

2 / 5

Actionability

Guidance is fully executable throughout: exact commands ("git diff --cached", "git rev-parse --verify <argument>", "git log --oneline --reverse <ref>..HEAD", "git show <commit-hash>"), ready-to-emit AskUserQuestion prompts with options, concrete flag-routing examples ("+check +coupling 123"), and complete copy-paste JSON gate blocks including a worked failure example — matching the 5 anchor's coverage of common cases.

5 / 5

Workflow Clarity

The routing chain (empty → staged, PR URL/digits → PR, validate ref → commits or ask), per-mode numbered steps, commit-count checkpoint, freshness checks, and the validate-then-recompute marker lifecycle form a clear sequence with explicit validation steps, error-recovery paths (re-validate a corrected ref, re-run /aif-review +check), and checklists — the 5 anchor. The review is read-only, so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

References are one level deep, clearly signaled with purpose (PR-SOURCE.md, CHECK-MODE.md, SEVERITY.md, COUPLING-REVIEW.md, API-COMPATIBILITY.md, pr-source.mjs, check-workflow.mjs — all verified present in ./references/), and heavy procedures are appropriately split out. The gap versus a 5: the multi-page marker/gate semantics are inlined in the body while also living in CHECK-MODE.md, so the body is not a lean overview.

4 / 5

Total

16

/

20

Passed

Description

83%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 strong description: clear third-person statement of capabilities with an explicit 'Use when' clause containing natural trigger phrases. Its main gaps are the unmentioned commits/git-ref review mode and mild overlap risk with generic code-review skills. Voice is correctly third person, so no specificity penalty applies.

DimensionReasoningScore

Specificity

"Perform code review on staged changes or a pull request" and "Checks for bugs, security issues, performance problems, and best practices" list several concrete actions, but the commits/git-ref mode (e.g. "/aif-review main") is not mentioned and the +check sentence drifts into mechanism detail rather than capability — minor gaps, not the comprehensive coverage of the 5 anchor.

4 / 5

Completeness

The description explicitly answers both questions: what ("Perform code review on staged changes or a pull request. Checks for bugs, security issues, performance problems, and best practices") and when, with concrete trigger phrases ("Use when user says 'review code', 'check my code', 'review PR', or 'is this code okay'"), matching the 5 anchor exactly.

5 / 5

Trigger Term Quality

"review code", "check my code", "review PR", "is this code okay" are natural phrases users would actually say, matching the 4 anchor's good coverage; common variations like "code review", "review my changes", or "is this PR ready" are missing, so not a 5.

4 / 5

Distinctiveness Conflict Risk

The triggers are specific to code review and mostly distinct from sibling skills, but "review code"/"review PR" overlap any generic or built-in code-review capability, so minor overlap risk with a closely related skill keeps it at the 4 anchor rather than 5.

4 / 5

Total

17

/

20

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.

Validation — 14 / 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

lee-to/ai-factory

Path

skills/aif-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.