mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-10 02:24:35 +08:00
854464b221
主要变更： - 模板重命名：采用优先级前缀（01-通用, 02-专用, 03-领域特定） - 目录调整：bug-diagnosis从development移至analysis - 引用更新：5个命令文件中21处模板引用更新为新路径 - 路径统一：所有引用统一使用完整路径格式 模板变更详情： - analysis/：8个模板（01-trace-code-execution, 01-diagnose-bug-root-cause等） - development/：5个模板（02-implement-feature, 02-refactor-codebase等） - planning/：5个模板（01-plan-architecture-design, 02-breakdown-task-steps等） - memory/：1个模板（02-document-module-structure） 命令文件更新： - cli/mode/bug-diagnosis.md（6处引用） - cli/mode/code-analysis.md（6处引用） - cli/mode/plan.md（6处引用） - task/execute.md（1处引用） - workflow/tools/test-task-generate.md（2处引用） 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
56 lines
2.0 KiB
Plaintext
56 lines
2.0 KiB
Plaintext
Debug and resolve issues systematically in the codebase.
|
|
|
|
## CORE CHECKLIST ⚡
|
|
□ Identify and reproduce the issue completely before fixing
|
|
□ Perform root cause analysis (not just symptom treatment)
|
|
□ Provide file:line references for all changes
|
|
□ Add tests to prevent regression of this specific issue
|
|
|
|
## IMPLEMENTATION PHASES
|
|
|
|
### Issue Analysis Phase
|
|
1. Identify and reproduce the reported issue
|
|
2. Analyze error logs and stack traces
|
|
3. Study code flow and identify potential failure points
|
|
4. Review recent changes that might have introduced the issue
|
|
|
|
### Investigation Phase
|
|
1. Add strategic logging and debugging statements
|
|
2. Use debugging tools and profilers as appropriate
|
|
3. Test with different input conditions and edge cases
|
|
4. Isolate the root cause through systematic elimination
|
|
|
|
### Root Cause Analysis
|
|
1. Document the exact cause of the issue
|
|
2. Identify contributing factors and conditions
|
|
3. Assess impact scope and affected functionality
|
|
4. Determine if similar issues exist elsewhere
|
|
|
|
### Resolution Phase
|
|
1. Implement minimal, targeted fix for the root cause
|
|
2. Ensure fix doesn't introduce new issues or regressions
|
|
3. Add proper error handling and validation
|
|
4. Include defensive programming measures
|
|
|
|
### Prevention Phase
|
|
1. Add tests to prevent regression of this issue
|
|
2. Improve error messages and logging
|
|
3. Add monitoring or alerts for early detection
|
|
4. Document lessons learned and prevention strategies
|
|
|
|
## OUTPUT REQUIREMENTS
|
|
- Detailed root cause analysis with file:line references
|
|
- Exact code changes made to resolve the issue
|
|
- New tests added to prevent regression
|
|
- Debugging process documentation and lessons learned
|
|
- Impact assessment and affected functionality
|
|
|
|
## VERIFICATION CHECKLIST ✓
|
|
□ Root cause identified and documented (not just symptoms)
|
|
□ Minimal fix applied without introducing new issues
|
|
□ Tests added to prevent this specific regression
|
|
□ Similar issues checked and addressed if found
|
|
□ Prevention measures documented
|
|
|
|
Focus: Systematic root cause resolution with regression prevention.
|