bug-killer

End-to-end debugging across frontend, gateway, and backend services uses a deterministic observe, hypothesize, and test loop to reproduce, isolate, and verify defects. This coordinated diagnostic cycle minimizes manual investigation across multi-service changes.

Git branch management during debugging uses a CURRENT mode with safe transitions to maintain a clean state. It integrates branch handling directly into the diagnostic workflow, supporting Jira-named branches for automated planning and progress tracking.

Yes, executing the diagnostic loop requires Claude Code permissions along with shell command and Git access. These permissions allow the workflow to run diagnostic steps, interact with data stores, and record plan artifacts automatically.

The observe hypothesize test loop reproduces and isolates defects by observing symptoms, forming a hypothesis about the root cause, and testing fixes iteratively. It spans UI, API, and data store interactions for guided, verifiable resolution.

Yes, this workflow specifically targets multi-service debugging scenarios where changes touch the UI, API, and data stores. It coordinates frontend and backend service interactions through interactive planning and iterative fixes.

A deterministic debugging loop provides a repeatable diagnostic cycle that replaces ad hoc manual investigation. It ensures defects are reproduced, isolated, and verified through structured progress tracking and automated planning artifacts.