Trace fix

Guarded development workflows for Claude Code — investigation before fixes, orchestration before implementation, verification before completion

Install

npx -y skills add cukas/claude-workflow-skills --skill trace-fix

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

Copied from the file, not written here

Use when fixing a bug, unexpected behavior, or test failure. Investigation-first TDD loop that traces root cause before touching code.

2.0 KB, 435 tokens by cl100k_base, as published. Nobody here has run it

Trace the root cause, then fix it with tests. Fully autonomous.

Read every file involved — use Read, Grep, Glob to trace the full call chain from entry point to where it breaks
Document the root cause — state what is wrong, where, and why. Not symptoms — the actual cause
If uncertain — say so explicitly. Do not guess. List hypotheses ranked by likelihood

Never edit a file you haven't read. Never propose a fix before tracing.

Write a failing test that reproduces the exact bug. Place it adjacent to the module under test using the project's existing test framework
Run the test — confirm it fails for the right reason
Implement the minimal fix — smallest change that makes the test pass
Run the full test suite + type checker
If any test fails — analyze the failure, adjust the fix, go back to step 7
If 5 iterations pass without all tests green — STOP. Present what you've tried, what failed, and ask the user for direction. Do not spin indefinitely

Document assumptions at the top of your first response before writing test code.

Invoke review-gate — execute the review-gate skill now. Do not summarize or declare done until review-gate has completed and all findings are resolved

Read before edit — always. No exceptions
If no test framework exists: state this, write the fix without TDD, but still trace first
If no type checker exists: skip type checking, proceed with tests
Do not ask clarifying questions — make reasonable assumptions and document them
Do not show intermediate results — present final diff and test results when green
If patrol plugin is active and fires a warning: comply immediately. Read the files it flags before continuing

Read from the repository

Just SKILL.md. No reference files, no scripts.