← ClaudeAtlas

bug-fixlisted

Plan and implement a bug fix — based on investigation, with quality checks and test verification
event4u-app/agent-config · ★ 7 · AI & Automation · score 84
Install: claude install-skill event4u-app/agent-config
# bug-fix ## Instructions ### 1. Check for prior investigation - Check if `/bug-investigate` was run in this conversation (context should be loaded). - If not, ask: ``` ⚠️ Has the bug already been analyzed? 1. Yes — I have the context from the previous analysis 2. No — run /bug-investigate first 3. I already know the root cause — start fixing directly ``` If option 3, ask for a brief description of the root cause and affected files. ### 2. Plan the fix Based on the root cause analysis, create a fix plan: ``` ═══════════════════════════════════════════════ 🔧 FIX-PLAN ═══════════════════════════════════════════════ 🐛 Bug: {brief description} 📍 Ursache: {root cause} 🎫 Ticket: {ticket ID or "none"} ─────────────────────────────────────────────── CHANGES: ─────────────────────────────────────────────── 1. 📁 {file1.php} → {what to change and why} 2. 📁 {file2.php} → {what to change and why} 3. 🧪 Tests → {which tests to add/update} ─────────────────────────────────────────────── RISIKO-CHECK: ─────────────────────────────────────────────── Side effects: {potential side effects} Similar spots: {other code that might need the same fix} Migration needed: {yes/no} Breaking change: {yes/no} ═══════════════════════════════════════════════ > 1. Yes — start implementing > 2. No — adjust the plan > 3. Cancel ``` ### 3. Implement the fix For each change: 1. **Read the file** before modifying. 2. **Make the change** with the file-edit