45 lines
1.2 KiB
Markdown
45 lines
1.2 KiB
Markdown
|
# Fix bug
|
||
|
|
|
||
|
|
## Configuration
|
||
|
|
- **Artifacts Path**: {@artifacts_path} → `.zenflow/tasks/{task_id}`
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Agent Instructions
|
||
|
|
|
||
|
|
If you are blocked and need user clarification, mark the current step with `[!]` in plan.md before stopping.
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Workflow Steps
|
||
|
|
|
||
|
|
### [x] Step: Investigation and Planning
|
||
|
|
<!-- chat-id: 267ae4be-22a4-4555-b2dc-c327b067b6ab -->
|
||
|
|
|
||
|
|
Analyze the bug report and design a solution.
|
||
|
|
|
||
|
|
1. Review the bug description, error messages, and logs
|
||
|
|
2. Clarify reproduction steps with the user if unclear
|
||
|
|
3. Check existing tests for clues about expected behavior
|
||
|
|
4. Locate relevant code sections and identify root cause
|
||
|
|
5. Propose a fix based on the investigation
|
||
|
|
6. Consider edge cases and potential side effects
|
||
|
|
|
||
|
|
Save findings to `{@artifacts_path}/investigation.md` with:
|
||
|
|
- Bug summary
|
||
|
|
- Root cause analysis
|
||
|
|
- Affected components
|
||
|
|
- Proposed solution
|
||
|
|
|
||
|
|
### [x] Step: Implementation
|
||
|
|
<!-- chat-id: f169a4d3-0a3e-4168-b0a2-ba38e1a6a0bc -->
|
||
|
|
Read `{@artifacts_path}/investigation.md`
|
||
|
|
Implement the bug fix.
|
||
|
|
|
||
|
|
1. Add/adjust regression test(s) that fail before the fix and pass after
|
||
|
|
2. Implement the fix
|
||
|
|
3. Run relevant tests
|
||
|
|
4. Update `{@artifacts_path}/investigation.md` with implementation notes and test results
|
||
|
|
|
||
|
|
If blocked or uncertain, ask the user for direction.
|