CtrlK
BlogDocsLog inGet started
Tessl Logo

workflow-test-fix-cycle

End-to-end test-fix workflow generate test sessions with progressive layers (L0-L3), then execute iterative fix cycles until pass rate >= 95%. Combines test-fix-gen and test-cycle-execute into a unified pipeline. Triggers on "workflow:test-fix-cycle".

62

Quality

73%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/workflow-test-fix-cycle/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%

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

This skill provides a comprehensive and actionable workflow with excellent workflow clarity, explicit validation gates, and concrete code examples. However, it suffers significantly from verbosity — information is repeated across multiple sections (agents listed 3 times, flow described in diagram + text + checklist), and the SKILL.md contains detailed content that should be delegated to the referenced phase documents. The skill would benefit greatly from aggressive trimming to serve as a true orchestrator overview.

Suggestions

Remove the large ASCII architecture diagram and task pipeline diagram — the execution flow section already conveys the same information more clearly and concisely.

Consolidate agent references to a single section instead of listing them in Architecture Overview, Phase Execution, and Related Skills separately.

Move the Output Artifacts directory structure and detailed error handling table to a referenced support file, keeping only a brief summary in SKILL.md.

Remove the Coordinator Checklist section as it largely duplicates the Core Rules and Phase Execution sections.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~350+ lines with extensive ASCII diagrams, repeated information across sections (agents listed 3 times, execution flow described twice), and explanations of concepts Claude already understands. The architecture diagram, task pipeline diagram, and execution flow all convey overlapping information. The coordinator checklist largely repeats the core rules and phase execution sections.

1 / 3

Actionability

The skill provides concrete, executable code examples for spawn_agent/wait_agent/close_agent/followup_task with proper parameters, specific CLI usage examples with multiple modes, exact file paths for outputs, and precise thresholds (95% pass rate, 10 max iterations). The error handling table maps specific scenarios to specific actions.

3 / 3

Workflow Clarity

The multi-step workflow is clearly sequenced with explicit phases, sub-phases, and validation checkpoints. The mandatory confirmation gate between Phase 1 and Phase 2 is emphasized repeatedly. The execution flow section provides a clear decision tree with pass rate thresholds, strategy escalation (conservative → aggressive → surgical), and error recovery including regression rollback. Feedback loops are explicit.

3 / 3

Progressive Disclosure

The skill correctly references phase docs (phases/01-test-fix-gen.md, phases/02-test-cycle-execute.md) for detailed execution, which is good progressive disclosure. However, no bundle files are provided to verify these references exist, and the SKILL.md itself contains far too much inline detail that should be delegated to those phase docs — the architecture diagram, detailed task pipeline, full directory structure, and repeated agent listings all bloat the overview.

2 / 3

Total

9

/

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.

The description is technically detailed and specific about what the skill does and when it triggers, making it strong on specificity and distinctiveness. However, the trigger terms are overly technical and command-oriented ('workflow:test-fix-cycle') rather than reflecting natural user language, which could limit discoverability when users describe their needs in plain English. The description would benefit from including more natural language trigger phrases alongside the command-style trigger.

Suggestions

Add natural language trigger terms users might say, such as 'run tests and fix failures', 'test suite repair', 'fix failing tests', or 'automated test debugging'

Rephrase the 'Triggers on' clause to include both the command trigger and natural language scenarios, e.g., 'Use when the user wants to run a full test-and-fix cycle, mentions fixing test failures iteratively, or invokes workflow:test-fix-cycle'

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: generate test sessions with progressive layers (L0-L3), execute iterative fix cycles, specifies a pass rate threshold (>= 95%), and names the sub-skills it combines (test-fix-gen and test-cycle-execute).

3 / 3

Completeness

Clearly answers both 'what' (generate test sessions with progressive layers, execute iterative fix cycles until 95% pass rate, combines two sub-skills) and 'when' (triggers on 'workflow:test-fix-cycle'). The trigger is explicit, though it's a command-style trigger rather than natural language guidance.

3 / 3

Trigger Term Quality

Includes some relevant terms like 'test-fix workflow', 'test sessions', 'fix cycles', and the explicit trigger 'workflow:test-fix-cycle', but these are mostly technical/internal identifiers rather than natural language terms a user would say. Missing common variations like 'run tests', 'fix failing tests', 'test suite', etc.

2 / 3

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: it's a unified pipeline combining specific sub-skills (test-fix-gen and test-cycle-execute) with a specific trigger command. The L0-L3 layer system and 95% pass rate threshold further distinguish it from generic testing skills.

3 / 3

Total

11

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

10

/

11

Passed

Repository
catlog22/Claude-Code-Workflow
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.