Take a ticket to reviewer-ready
Turn a ticket or bug report into a proven root cause, a minimal patch, and a clean handoff a reviewer can trust.
Use this when
Use this when a real but loosely written ticket, bug report, or customer complaint needs to become a bounded engineering change with enough proof for a fast review.
How it runs
- State the expected and actual behavior, then reproduce the failure in the smallest representative environment.
- Trace the behavior to a root cause and confirm the causal link with evidence.
- Implement the smallest credible fix, avoiding unrelated cleanup or hidden refactors.
- Repeat the original reproduction, run relevant regression checks, and package the result for review.
Done when
✓ The failure is fixed, verified, and ready for review. The issue reproduces before the fix, no longer reproduces afterward, and relevant regression checks pass.
Why it works
The loop closes the gap between something being wrong and a reviewer being able to trust the patch. Reproduction, evidence, bounded scope, and a structured handoff remove the detective work from review.
Implementation note
Match the proof to the failure: screenshots or recordings for UI issues, tests or logs for backend behavior, benchmark deltas for performance, and sanitized traces for integrations.
More debugging loops
Memory leak hunt
Drive a suspected memory leak to ground: reproduce growth under a repeated workload, capture heap snapshots, and fix the retention until memory stays flat.
Keep asking for valid input
Loop until the user enters a number that passes your validation criteria.
Ralph the bug backlog
Work a triaged bug list one fix per fresh-context iteration: reproduce first, fix minimally, prove it with a regression test, and log root-cause patterns to guardrails.