CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-review

Review changed code against project standards. Checks for missing tests, dead code, type safety, lint issues, and coding conventions. Run after completing any implementation work.

Quality

81%

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

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

An exceptionally actionable, well-sequenced review workflow with concrete verification commands and explicit severity tiers — close to ideal on actionability and workflow clarity. Its weaknesses are structural: the entire project-standards corpus is inlined in one ~570-line file with no reference files, costing both token efficiency and progressive disclosure.

Suggestions

Move the domain-standards sections (Bank/Tenant Isolation, HTTP Middleware, Outbound HTTP, Concurrency, Database Locking, Text in SQL, Documentation Code Examples) into a references/ file (e.g. references/standards.md) and keep only a one-line summary per standard in SKILL.md, with the review steps linking to each — this would improve both conciseness and progressive_disclosure.

De-duplicate rules stated twice: the pagination shape is fully specified in both "API Layer & Data Access" and step 7d, and bank-isolation tells appear in both the standards section and step 7c; state each rule once and have the step reference it.

Trim justificatory narratives (e.g. the BaseHTTPMiddleware rps/p99 numbers and issue history, the full integrations.json mechanics in step 9) to the one-sentence reason needed to apply the rule, moving the incident history to a reference if it must be kept.

DimensionReasoningScore

Conciseness

The body is dense with genuinely project-specific knowledge, but at ~570 lines (~12K tokens) all inlined it includes duplicated rule statements (pagination appears in both "API Layer & Data Access" and step 7d) and long justificatory narratives (BaseHTTPMiddleware performance history, integrations.json mechanics) that could be tightened or trimmed.

3 / 5

Actionability

Guidance is fully executable throughout: copy-paste grep commands per risk class, exact file paths and script names, BAD/GOOD code examples, and explicit must-fix/should-fix/note severity classifications for findings.

5 / 5

Workflow Clarity

Thirteen clearly sequenced steps with explicit validation checkpoints — per-risk grep verification, "construct the concrete two-bank scenario ... to confirm it's real before flagging", and a severity-organized reporting checklist — matching the anchor-5 profile of sequence plus validation plus checklists. A minor flaw (steps 11b–11h appear out of alphanumeric order) does not break the sequence.

5 / 5

Progressive Disclosure

Section headers are clear, but there are no bundle files at all and ~400 lines of domain standards (SQL isolation, middleware, concurrency, docs conventions) are inlined in SKILL.md where they clearly belong in separate reference files — matching the anchor-3 example of well-headed content that should be split out.

3 / 5

Total

16

/

20

Passed

Description

80%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: it names the domain, lists five concrete capabilities, and includes an explicit activation trigger in third-person voice. The main gap is trigger-term breadth — no mention of the natural phrases (PR, pull request, diff) a user would say when invoking a code review.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete actions — "Checks for missing tests, dead code, type safety, lint issues, and coding conventions" — matching the comprehensive multi-action coverage of the anchor-5 example rather than the minor-gaps profile of anchor 4.

5 / 5

Completeness

Both a clear "what" (the specific checks) and an explicit "when" ("Run after completing any implementation work") are present, so the missing-trigger cap at 3 does not apply, but the "when" clause lacks the concrete trigger phrases that distinguish anchor 5.

4 / 5

Trigger Term Quality

Natural terms like "Review changed code", "lint issues", "missing tests", and "dead code" are present, but common user variations such as "PR", "pull request", or "diff" are missing, placing it just below the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Review changed code against project standards" plus the specific check list carves a mostly distinct niche, but the broad code-review framing leaves minor overlap risk with generic review skills, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (575 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

13

/

16

Passed

Repository

vectorize-io/hindsight

Path

.claude/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.