CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review-tests

Use when checking whether a branch is adequately tested — building and running the affected workspaces, then auditing changed code for missing test files, untested exports, untested error paths and untested routes — and reporting gaps with T-M/U/E/R/S IDs in the four-field format.

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

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 unusually actionable, well-sequenced audit procedure with real validation checkpoints and error recovery — commands are copy-paste ready and every rule is repo-specific rather than generic. Its weaknesses are token efficiency (the report-shape rule is enforced through repetition rather than one statement plus a check) and a monolithic single-file layout that inlines detail a references/ bundle would carry better.

Suggestions

Split the tautological-test shapes and the "cost more than they catch" catalogue into a references/ file (e.g. references/test-shapes.md), keeping a one-line pointer in Step 4 — that alone would cut roughly a quarter of the body.

State the five-heading rule once in Step 0 and have the mid-run and final checks reference it ("re-run the Step 0 shape check") instead of restating the heading list and the disallowed `## Summary`/`## Verdict` headings three times.

Move the whole-package sweep mode paragraph out of Step 4 into its own reference or a clearly separate section — it is a different task from the branch audit that dominates the file, and interleaving it makes the branch workflow harder to follow.

DimensionReasoningScore

Conciseness

The body is dense and repo-specific with no explanation of concepts Claude already knows, but the five-heading shape rule is restated four times (Step 0, the bold "only ever edited, never rewritten" paragraph, the mid-run "Check the shape once" block, and the final "Check the file before you finish" section) and the disallowed-heading list (`## Summary`, `## Verdict`, `## Scope and method`, `## Bottom line`) is repeated three times. Not 4: that repetition exceeds "minor instances that could be trimmed"; not 2: nearly every sentence carries non-generic, actionable instruction.

3 / 5

Actionability

Fully executable throughout: exact commands for base resolution (`git config --get branch.$(git branch --show-current).gh-merge-base`), builds and tests (`bun run --cwd <workspace-path> test:run`), mutation testing (`STRYKER_TESTS='tests/lib/money.test.ts' bun run --cwd cire/api test:mutation --base "$DIFF_BASE"`), a verbatim heredoc report skeleton, grep shape checks with expected outputs ("It must print `5`"), and an exact four-field finding format. Specific examples cover the common cases.

5 / 5

Workflow Clarity

Clear Step 0–5 sequence with explicit validation checkpoints (the shape check "as soon as the first gap is in the file", the final two grep counts both required to print 5) and genuine error-recovery loops: restore the skeleton and re-edit if the count is low, and defined handling for `no changed source lines`, `No tests were executed`, and a `0.00` tests-per-mutant run. "No step is a stop" tells the model how to proceed past every failure mode.

5 / 5

Progressive Disclosure

No bundle files exist and all content sits inline in one ~290-line file. Section structure and navigation are good, but bulk detail that belongs in reference files is inlined: the tautological-test shape catalogue, the mutation-testing log-interpretation rules, and the whole-package sweep mode paragraph. Not 4: the split is more than a "minor organization gap" for a file this size; not 2: the file is well-sectioned, not a monolithic wall.

3 / 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: concrete, third-person, explicit about both what it does and when to use it, with a distinctive reporting format that separates it from generic review skills. The only weakness is a single trigger phrasing where synonyms (e.g. "test coverage", "what tests are missing") would broaden natural activation.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "building and running the affected workspaces", "auditing changed code for missing test files, untested exports, untested error paths and untested routes", "reporting gaps with T-M/U/E/R/S IDs in the four-field format" — covering the workflow end to end. Not 4: the action list has no gaps within its domain.

5 / 5

Completeness

Both are explicit: the what (build, run tests, audit changed code for four gap classes, report with tiered IDs) and the when ("Use when checking whether a branch is adequately tested"). Not 5: the when-clause is a single trigger condition with no additional concrete trigger variations or synonyms.

4 / 5

Trigger Term Quality

Natural phrases a user would say are present: "branch", "adequately tested", "missing test files", "untested exports", "untested error paths", "untested routes". Not 5: common variations like "test coverage", "coverage gaps", or "review the tests" are missing; not 3: keyword coverage is good and phrased in user language, not jargon.

4 / 5

Distinctiveness Conflict Risk

Clear niche — branch test-adequacy auditing with a bespoke T-M/U/E/R/S reporting format — that no generic skill description would duplicate. Not 4: the trigger and output format are specific enough that overlap with even closely related review skills is minimal.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 possibly missing (scripts/check-wikilinks.ts, scripts/tests/)

Warning

Total

15

/

16

Passed

Repository

englishstreetventures/osn

Path

.claude/skills/review-tests/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.