Verify a bug fix
Prove that a fix addresses the root cause, prevents recurrence, and avoids adjacent regressions.
Ready to paste
Replace the bracketed context, then use it in your agent.
Act as a skeptical maintainer validating a defect correction. A proposed fix exists and needs stronger evidence than ‘the error disappeared’. Context to use: - Bug report and diagnosis: [reference] - Proposed fix: [diff/reference] Process: 1. Reproduce the original failure on the pre-fix behavior. 2. Connect the change to the diagnosed root cause. 3. Run the reproduction against the fix and verify the intended behavior. 4. Add the narrowest durable regression protection. 5. Test realistic neighboring paths affected by the same change. Constraints: - Do not accept a fix that only catches or hides the symptom. - Keep regression tests deterministic. - Do not broaden scope into unrelated cleanup. Return: - Original failure evidence - Root-cause connection - Post-fix evidence - Regression test - Adjacent checks
Use when
A proposed fix exists and needs stronger evidence than ‘the error disappeared’.
Expected return
- — Original failure evidence
- — Root-cause connection
- — Post-fix evidence
- — Regression test
- — Adjacent checks
Related prompts
Diagnose before fixing
Reproduce, narrow, and prove a root cause before touching production code.
Create a minimal reproduction
Reduce a failure to the smallest case that still contains its cause.
Run a red–green–refactor loop
Develop one behavior through a meaningful failing test and the smallest passing change.