CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

regression-suite

Map test coverage to GDD critical paths, find fixed bugs lacking regression tests, flag drift from new features.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/regression-suite/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 workflow skill: exact globs, grep patterns, verbatim prompts, complete output templates, and explicit guards with named recovery paths for every failure mode. Its weaknesses are token cost from repeating the qa.level guard and cross-skill meta-commentary, and inlined templates that inflate the file to ~330 lines with no bundle files distributing detail.

Suggestions

State the qa.level: minimal stop once in Section 1 and reference it from the intro and Section 7 verdict list instead of re-explaining it in each place.

Trim the zero-denominator blockquote to the operative rule — drop the /scope-check cross-reference and the quoted wording from the other skill.

Move the report and suite-manifest templates to a references/templates.md file and keep only field summaries in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense project-specific instruction with no teaching of known concepts, but the "qa.level: minimal" stop is explained three times (intro paragraph, Section 1, Section 7 verdicts) and the denominator blockquote spends lines on cross-skill meta-commentary ("This is the same defect /scope-check carries a Phase 4 guard against, in the same words"). Not 4 because the repetition and quoted /scope-check wording exceed minor over-explanation; not 2 because there is no generic padding and nearly every line is operational.

3 / 5

Actionability

Concrete globs ("tests/unit/**/*_test.*"), exact tool usage ("Grep tool (pattern ^#, content mode)" with Read offset/limit), verbatim AskUserQuestion prompt text, and complete report and manifest markdown templates make the guidance copy-paste ready. Placeholders like "[Engine-specific command to run all regression tests]" are justified engine-agnostic flexibility rather than pseudocode, so this sits at the fully-executable anchor rather than the 4 anchor's 'minor gaps'.

5 / 5

Workflow Clarity

A seven-step numbered sequence with explicit validation checkpoints and error recovery: the early guard ("STOP here, before any scan"), the zero-denominator guard ("do not emit a percentage"), the smoke-report stop naming the fix ("run /smoke-check first"), ask-before-write gating, and a first-match-wins verdict list. Not 4 because checkpoints are explicit feedback loops with named recovery actions rather than implicit or partially present.

5 / 5

Progressive Disclosure

Well-organized numbered sections with clearly signaled one-level-deep pointers to project docs (".claude/docs/automation-modes.md", ".claude/docs/workflow-modes.md", ".claude/docs/config-resolution.md"), and no bundle files exist to nest. Not 5 because at ~330 lines the full manifest and report templates are inlined where a references/ file could carry them; not 3 because structure and navigation are clean with no buried references.

4 / 5

Total

17

/

20

Passed

Description

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

The description states three concrete, domain-specific actions and is clearly distinguishable from generic testing skills, but it omits any explicit when-to-use guidance, which caps completeness and leaves natural trigger-term coverage thin. Adding a 'Use when...' clause and user-voiced phrases like 'regression suite' or 'coverage gaps' would raise it substantially.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use after fixing a bug, before a phase gate, or at sprint close to check regression coverage.'

Include natural trigger phrases users would actually say — 'regression suite', 'regression test', 'test coverage gaps', 'coverage report' — alongside the existing 'test coverage'.

Pair 'GDD critical paths' with a plain-language gloss (e.g., 'game design acceptance criteria') so the trigger fires for users who don't know the acronym.

DimensionReasoningScore

Specificity

"Map test coverage to GDD critical paths" and "find fixed bugs lacking regression tests" are concrete, domain-anchored actions, listing several specific capabilities with minor gaps. Not 5 because "flag drift from new features" is comparatively abstract and the description omits suite-manifest maintenance and reporting modes; not 3 because three specific actions exceed the '1-2 concrete actions' anchor.

4 / 5

Completeness

The 'what' is clear (map coverage, find untested bug fixes, flag drift), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3. Not 2 because the 'what' is concrete rather than vague; not 4 because 'when' is wholly absent, not merely implicit or underspecified.

3 / 5

Trigger Term Quality

Relevant keywords are present ("test coverage", "regression tests", "bugs") but common natural variations are missing — "regression suite", "test gaps", "coverage report" — and "GDD critical paths" is project jargon users may not voice. Not 4 because natural trigger phrasing users would actually say is largely absent; not 2 because several real, relevant keywords exist rather than one or two generic ones.

3 / 5

Distinctiveness Conflict Risk

"Map test coverage to GDD critical paths, find fixed bugs lacking regression tests" carves a distinct regression-suite niche with only minor overlap risk against generic test-writing skills. Not 5 because without explicit triggers a broad 'write tests' request could still route here; not 3 because the GDD/regression-suite framing is specific to this niche rather than broadly overlapping.

4 / 5

Total

14

/

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

Donchitos/Claude-Code-Game-Studios

Path

.claude/skills/regression-suite/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.