CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review

Review the current working diff for correctness bugs plus reuse, simplification, and efficiency cleanups. Use when the user asks to review their changes, review the diff, or sanity-check code before committing or pushing. Honour requested review depth and optional comments or fixes only when supported by current tools and task authority.

Quality

82%

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

71%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 delivers a clear, actionable review procedure with concrete git commands and a defined finding format, appropriately self-contained for its size. Its main weakness is prose that references undefined external obligations ("review-ledger", "copied wrapper") which reads as leftover context from another environment and costs clarity.

Suggestions

Remove or rewrite the meta-commentary in the intro ("this copied wrapper does not prove that a built-in review, effort control or paid review mode is available") so the skill reads as instructions for this environment, not notes about its provenance.

Replace the undefined obligation reference ("Project review-ledger, independence, provider and publication requirements remain binding") with either the concrete requirements themselves or a pointer to where they are defined.

Add the explicit git command for the pinned base/HEAD comparison in step 3 (e.g., `git diff <base>..<HEAD>`) to make the branch-review path as executable as the working-diff path.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes unnecessary or confusing material: "this copied wrapper does not prove that a built-in review, effort control or paid review mode is available" is meta-commentary about the skill's provenance, and "Project review-ledger, independence, provider and publication requirements remain binding" references obligations never defined here. This matches the 3 anchor (mostly efficient, some unnecessary explanation) rather than the 4 anchor's "minor instances that could be trimmed", since these sentences cost real comprehension, not just tokens.

3 / 5

Actionability

Concrete, executable commands are given (`git status --short`, `git diff`, `git diff --staged`, explicit reads for untracked files) plus a specific finding format ("`file:line`, a one-sentence defect statement, and a concrete failure scenario") and effort-to-breadth mapping. Minor gaps keep it below fully copy-paste-ready: the pinned base/HEAD comparison is described ("a comparison of the pinned base/HEAD commits") without the actual command, and "check the current host's command/skill inventory" lacks a concrete mechanism.

4 / 5

Workflow Clarity

A clear three-step sequence (establish scope, use supported tooling, local fallback with recursion guard) with most checkpoints present: drift check before reporting, explicit untracked-file handling, ranked findings, and the "Never invent findings" guard. This is a read-only review skill, so the destructive/batch validation cap does not apply; it sits at the 4 anchor (clear sequence, most checkpoints) rather than 5 because finding-verification feedback loops are only implicit.

4 / 5

Progressive Disclosure

This is a single-file skill under 50 lines with no references/, scripts/, or assets/ directories and no need for external files; the short body is well-organized into a numbered procedure with bold step labels and clear navigation. Per the simple-skill guidance, that merits a 5 — nothing is inlined that belongs in a separate file.

5 / 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 that clearly states what the skill does and when to use it, with natural trigger phrases and concrete review categories. The only weakness is a slightly hedged closing clause about tooling authority that dilutes capability coverage without adding trigger value.

DimensionReasoningScore

Specificity

"Review the current working diff for correctness bugs plus reuse, simplification, and efficiency cleanups" lists several specific, concrete actions within the review domain. It falls short of the 5 anchor because the trailing conditional clause ("Honour requested review depth and optional comments or fixes only when supported by current tools") adds hedging rather than capability coverage, and it is not clearly above the 4 anchor's "minor gaps in coverage".

4 / 5

Completeness

It explicitly answers both questions: the "what" ("Review the current working diff for correctness bugs plus reuse, simplification, and efficiency cleanups") and the "when" with concrete trigger phrases ("Use when the user asks to review their changes, review the diff, or sanity-check code before committing or pushing"). This matches the 5 anchor's pattern of what + explicit when with trigger phrases, and exceeds the 4 anchor where the "when" is less specific.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: "review their changes", "review the diff", "sanity-check code before committing or pushing". A few common variations are missing (e.g., "code review", "review my code", "before I commit"), placing it at good-but-not-comprehensive coverage rather than the 5 anchor's synonym/extension completeness.

4 / 5

Distinctiveness Conflict Risk

Scoping to "the current working diff" and naming correctness bugs plus specific cleanup categories gives it a clear niche distinct from generic review/editing skills. Minor overlap risk remains with closely related skills (PR/branch review, commit-message generation), keeping it below the 5 anchor's minimal-conflict standard.

4 / 5

Total

17

/

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

BigSimmo/PsychSift

Path

.claude/cloud-profile/skills/code-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.