CtrlK
BlogDocsLog inGet started
Tessl Logo

review

Diff-scoped correctness review that reads the codebase around the change — callers, contracts, and invariants — and returns line-anchored findings ranked by severity with confidence, then a merge-risk verdict. Use for reviewing a PR, diff, or named change set. Not for style review, approvals-as-rubber-stamp, or editing the code.

74

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

The risk profile of this skill

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.

A tightly written, senior-level review playbook with concrete commands, a severity-ranked output template, and a real validation gate. The only improvement would be a worked example finding to make the output format fully self-modeling.

Suggestions

Add one short worked example of a finding rendered in the output format (e.g. a sample [severity: high] line with reachable path and fix) so the template is self-modeling.

Optionally surface the diff-base resolution as an explicit first step (e.g. how to determine <base> when unspecified) to remove the one remaining ambiguity in an otherwise executable workflow.

DimensionReasoningScore

Conciseness

Lean and efficient throughout; assumes Claude's competence (no explanation of git, callers, or basic review concepts) and every section earns its place, including the load-bearing framing in the opener.

5 / 5

Actionability

Provides copy-paste commands ('git diff <base>...HEAD', 'gh pr diff') and a complete output-format template, but lacks a fully-worked example finding rendered in that template to model the common case end-to-end.

4 / 5

Workflow Clarity

Clear sequence (Scope → What to hunt → Confidence gate → Output → Boundaries) with an explicit validation checkpoint in the confidence gate ('Report a finding only when you can name the reachable path') and a 'Considered, not findings' feedback channel; read-only so the destructive-cap does not apply.

5 / 5

Progressive Disclosure

Single-purpose skill with well-organized section headers and no monolithic wall of text; no external references are needed, so clean in-body structure fully satisfies progressive disclosure.

5 / 5

Total

19

/

20

Passed

Description

92%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 sharp, well-scoped description that concretely states capabilities, gives explicit trigger guidance, and draws clear boundaries against adjacent skills. The only gap is modest synonym coverage in the trigger terms.

Suggestions

Add a couple of common user phrasings (e.g. 'code review' or 'review my changes') to broaden trigger-term coverage.

Consider naming the diff base explicitly in the trigger clause (e.g. 'Use when reviewing a PR, a local diff, or a named change set') to widen distinctiveness.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'reads the codebase around the change — callers, contracts, and invariants', 'returns line-anchored findings ranked by severity with confidence', 'merge-risk verdict' — giving comprehensive coverage of what the review does.

5 / 5

Completeness

Explicitly answers both what ('diff-scoped correctness review… returns line-anchored findings… merge-risk verdict') and when ('Use for reviewing a PR, diff, or named change set') with concrete trigger phrases, so no cap applies.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('reviewing a PR, diff, or named change set') but misses common variations such as 'code review' or 'review my changes', leaving a few natural terms uncovered.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (diff-scoped correctness) with explicit 'Not for…' boundaries (style review, rubber-stamp approvals, editing), minimizing conflict with neighboring skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Hmbown/Codewhale
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.