Skill
Code Workflow
4-stage workflow for code changes: research → plan → user review → implement (TDD). Applies to all tasks requiring code changes: issue implementation, fix_pl...
When to use Code Workflow
Choose if
You want an agent to stop free-styling code changes and follow a deterministic research → plan → review → implement loop with TDD by default. Useful for larger refactors or feature work where the trade-off of one extra round-trip (the BLOCKED state for human review) is worth catching scope errors before any code is written.
Avoid if
The task is a trivial 1–2 line edit — the SKILL.md itself says to skip the full workflow there. Also avoid if your stack doesn't use GitHub-flow / TDD conventions or if the human reviewer isn't around to unblock the workflow at step 3; the skill will sit at STATUS: BLOCKED until they respond.
Risk Flags
- MEDIUM scope ClawHub moderation flagged this skill as "suspicious.llm_suspicious". Review the SKILL.md before adopting in production.
- LOW scope Depends on sibling topics (github-flow, skill-kit, tdd, ui-test) for PR creation, issue registration, and test execution. Without those installed the workflow degrades to manual handoffs.
Cost
Type: Free
Distribution
- ClawHub
code-workflow- License
- MIT-0