CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tdd-workflows-tdd-refactor

Refactor code while preserving passing tests and behavior. Use during the TDD refactor phase to remove duplication, improve design, and verify each structural change.

Quality

69%

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 ./skills/tdd-workflows-tdd-refactor/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The body contains a genuinely sound refactoring safety workflow — green baseline, incremental atomic changes, test after each step, commit checkpoints, and a revert-on-failure recovery protocol — but buries it under textbook knowledge catalogs (SOLID, design patterns, code smells) Claude already knows and generic template filler sections. The code example is illustrative rather than executable, and no operational commands (e.g., the actual test command) are specified.

Suggestions

Cut the textbook catalogs (SOLID definitions, GoF pattern lists, code-smell taxonomy) — Claude already knows these; keep only guidance on which techniques to prefer and in what order, or move them to a references/ file with clear pointers.

Remove the generic template filler (the circular "Use this skill when" / "Do not use this skill when" bullets and the boilerplate Instructions bullets) and fix the unclosed Prompt quote in the Usage section.

Specify the actual verification commands (e.g., the project's test runner invocation) instead of the generic "Run tests", and either make the TypeScript example self-contained or trim it to the essential diff.

DimensionReasoningScore

Conciseness

Quotes: "Single Responsibility: One reason to change", "Apply Creational (Factory, Builder, Singleton)", "Working on tdd workflows tdd refactor tasks or workflows" — multiple sections catalog textbook concepts Claude already knows (SOLID, GoF patterns, code smells) alongside circular template filler. Terse bullet formatting keeps it above a 1, but the padding is far more than "some".

2 / 5

Actionability

Quotes: "Duplicated code → Extract methods/classes", "Run tests to establish green baseline", "Profile to identify bottlenecks" — the smell→technique mappings and the full before/after example are concrete, but no executable commands are given (which test command? which profiler?) and the example references undefined types (OrderTotal, ValidationResult) with an incomplete Before snippet, leaving key details missing.

3 / 5

Workflow Clarity

Quotes: "Run tests to establish green baseline", "Make small, atomic changes", "Run tests after each modification", "If tests fail: Immediately revert last change" — a clear sequence with explicit validation checkpoints, a safety checklist, and a revert-on-failure recovery loop. It falls short of a 5 because the process is diluted across ten parallel catalog sections and the unclosed Prompt quote in Usage muddies the entry point.

4 / 5

Progressive Disclosure

The body runs ~185 lines with section headers (some structure), but the design pattern, SOLID, and advanced-pattern catalogs are inlined content that clearly belongs in a separate reference file, and there are no external file references at all — matching the anchor of content that should be separate sitting inline.

3 / 5

Total

12

/

20

Passed

Description

75%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 clearly states what the skill does and includes an explicit "Use during" trigger clause with several concrete actions (preserve tests, remove duplication, verify changes). Trigger coverage is narrow — it only fires on TDD-refactor-phase phrasing and misses natural synonyms like "clean up code" — which keeps most dimensions at 4 rather than 5.

Suggestions

Broaden the when clause to cover natural user phrasings, e.g. "Use when the user asks to refactor, clean up, or restructure code while keeping tests green, or during the TDD refactor (red-green-refactor) phase."

Add common trigger synonyms such as "code cleanup", "remove duplication", "improve code structure", and "keep tests green" so the skill fires outside formal TDD workflows.

DimensionReasoningScore

Specificity

Quotes: "Refactor code while preserving passing tests and behavior", "remove duplication, improve design, and verify each structural change" — several concrete actions are named, but "improve design" is abstract, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

Quotes: "Refactor code while preserving passing tests and behavior" (clear what) and "Use during the TDD refactor phase" (explicit when). Both are present, but the when clause offers a single narrow trigger phrase rather than the varied concrete trigger phrasings of the top anchor.

4 / 5

Trigger Term Quality

Quotes: "Refactor code", "Use during the TDD refactor phase", "remove duplication" — the core natural term "refactor" is present with related terms, but common variations users would say ("clean up code", "improve code structure", "keep tests green") are missing.

4 / 5

Distinctiveness Conflict Risk

Quote: "Use during the TDD refactor phase" — a clear niche with distinct framing around test-preserving refactoring, but there is minor overlap risk with general refactoring or code-quality skills since "Refactor code" alone is a broad lead-in.

4 / 5

Total

16

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

rmyndharis/antigravity-skills

Path

skills/tdd-workflows-tdd-refactor/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.