Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
How this command is triggered — by the user, by Claude, or both
Slash command
/mokata:bugmokata/templates/commands/The summary Claude sees in its command listing — used to decide when to auto-load this command
# mokata · /bug Start from a reproducer. Write a failing test that captures the bug, then fix to green and leave the test as a regression guard. Root-cause from the REAL code — read the failing path and trace it with the structural queries before fixing; don't guess at code you haven't read. Labels progress reported -> reproduced -> fixing -> verified; the fix is gated behind a reproducer. ## Gate (check) A bug fix requires a reproducer and a failing test before the fix. ## Standalone This command runs on its own — no upstream pipeline phase is required. It applies only its own gate abov...
Start from a reproducer. Write a failing test that captures the bug, then fix to green and leave the test as a regression guard. Root-cause from the REAL code — read the failing path and trace it with the structural queries before fixing; don't guess at code you haven't read. Labels progress reported -> reproduced -> fixing -> verified; the fix is gated behind a reproducer.
A bug fix requires a reproducer and a failing test before the fix.
This command runs on its own — no upstream pipeline phase is required. It applies only its own gate above, and never silently skips a gate of a phase you did run.
npx claudepluginhub jasgujral/mokata-oss/fixitFixes broken functionality from pasted error output, stack traces, or failing-behavior descriptions using a stepwise diagnostic workflow with TDD, research, and proof-of-work evidence.
/SKILLRapidly fixes small bugs and minor issues with root cause analysis and TDD verification. Accepts a bug description, finding ID, or direct finding input.
/TDD-debugDebugs a specified issue using TDD: writes a failing test, then fixes the bug via multi-agent collaboration (codex, gemini-cli, subagents), verifying the test passes.
/hatch3r-bug-pipelineRuns a test-first 3-phase bug fix pipeline: reproduce + root-cause, regression-test + fix, then root-cause-depth review. Delegates to four sub-agents in sequence.