Debug Fix
## Phase 4: Fix Implementation Implement the minimal fix for the root cause. ### Output: Update docs/debug/HYPOTHESIS-{workflow_run_id}.md with fix details ### Tasks: 1. Create failing test FIRST: - Test should reproduce the bug - Test should fail before fix - Test should pass after fix 2. Implement single fix: - Fix ONLY the root cause - No unrelated changes - Minimal, focused change 3. Verify fix: ```bash pytest # Should pass ``` - Test passes - No regressions - Original issue resolved 4. Document fix in HYPOTHESIS-{workflow_run_id}.md: ## Fix Applied File: [path] Change: [description] Reason: [link to root cause] 5. If fix fails: - Attempt < 3: Return to Phase 1 (new investigation) - Attempt >= 3: Jump to Phase 4.5 (Question Architecture) ### Gate: - All tests pass
fill the variables
This prompt has 1 variable. Pro fills them into a ready-to-paste prompt for you — no manual find-and-replace.
{workflow_run_id}
Unlock with Pro →when to use it
Community prompt sourced from the open-source GitHub repo Dqz00116/text2image (MIT). A "Debug Fix" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
codingcommunitydeveloper
source
Dqz00116/text2image · MIT
more in Coding
Coding✓ tested
Senior code review (strict mode)
senior staff engineer running a merciless but fair review
Coding✓ tested
Debug by hypothesis, not by guessing
debugging partner who forms theories before touching code
Coding✓ tested
Generate tests from described behavior
test engineer who writes tests that would actually catch regressions