regression-suite

Map test coverage to GDD critical paths, identify fixed bugs without regression tests, flag coverage drift from new features, and maintain tests/regression-suite.md. Run after implementing a bug fix or before a release gate.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, highly actionable multi-mode skill with a clear sequenced workflow and proper write-validation gates. It loses points mainly on conciseness and progressive disclosure, where large inline templates inflate the body and could be extracted into reference files.

Suggestions

Extract the full report-format and suite-manifest markdown templates (section 6) into a reference file such as references/manifest-template.md, keeping SKILL.md as a lean overview that links to it.

Tighten the duplicated guidance between section 5 (drift detection) and the report's drift section, and trim the restated mode descriptions that already appear in section 1.

Consider adding a brief bundle reference for the coverage-status taxonomy and recommended-test path conventions so the core workflow stays scannable.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining concepts Claude already knows, but at roughly 250 lines it carries two full inline markdown templates (report and manifest) plus some restated guidance that could be tightened, matching the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It gives concrete Glob patterns, Grep targets, exact file paths, a defined coverage status taxonomy, suggested test-file path patterns, and complete output templates, making the guidance copy-paste ready despite being instruction-only.	3 / 3
Workflow Clarity	Seven numbered sections form a clear sequence, and the destructive manifest write is gated by an explicit confirm-before-write checkpoint with a BLOCKED verdict fallback and a 'never remove existing entries' guardrail, satisfying the validation requirement.	3 / 3
Progressive Disclosure	No bundle files exist and all content is inline; sections are well organized, but the skill exceeds 50 lines and the large report/manifest templates are content that could be split into one-level-deep reference files.	2 / 3
	Total	10 / 12 Passed

Description

85%

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, specific description that clearly states what the skill does and when to run it, with a well-defined niche. Its only weakness is trigger-term breadth, relying on somewhat technical phrasing rather than a wide spread of natural user terms.

Dimension	Reasoning	Score
Specificity	The description lists four concrete actions ('Map test coverage to GDD critical paths', 'identify fixed bugs without regression tests', 'flag coverage drift from new features', 'maintain tests/regression-suite.md'), matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	It explicitly answers both what (the four actions) and when ('Run after implementing a bug fix or before a release gate'), providing equivalent explicit trigger guidance so completeness is not capped at 2.	3 / 3
Trigger Term Quality	It includes relevant terms like 'regression tests', 'bug fix', 'test coverage', and 'release gate', but leans on specialized jargon ('GDD critical paths', 'coverage drift') and lacks the breadth of natural user variations seen in the top anchor.	2 / 3
Distinctiveness Conflict Risk	The GDD-pipeline regression-suite niche is clearly scoped with distinct triggers and an explicit output artifact, making it unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 984023d

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.