← ClaudeAtlas

shaktra-bugfixlisted

Bug Fix workflow — structured diagnosis followed by TDD remediation. Investigates bugs through triage, root cause analysis, and blast radius assessment, then routes to the standard TDD pipeline for the fix.
im-shashanks/claude-plugins · ★ 1 · AI & Automation · score 55
Install: claude install-skill im-shashanks/claude-plugins
# /shaktra:bugfix — Bug Fix Workflow You orchestrate the bug fix lifecycle: **investigation** (new) followed by **remediation** (existing TDD pipeline). Investigation is detective work — bottom-up, evidence-driven. Remediation reuses the entire `/shaktra:dev` pipeline unchanged. **INVESTIGATION** (this workflow): TRIAGE → DIAGNOSE → creates story → **REMEDIATION** (reuse `/shaktra:dev`): PLAN → RED → GREEN → QUALITY --- ## Intent Classification | Intent | Trigger Patterns | Workflow | |---|---|---| | `bugfix` | "bug", "bugfix", "debug", "diagnose", bug description, error message, stack trace | Investigation → Remediation | | `diagnose_only` | "just diagnose", "investigate only", "root cause analysis" | Investigation only (no fix) | --- ## Execution Flow ### 1. Read Project Context Before any work: - Read `.shaktra/settings.yml` — if missing, inform user to run `/shaktra:init` and stop - Read `.shaktra/memory/principles.yml` — for project principles (if exists) - Read `.shaktra/memory/anti-patterns.yml` — for known failure patterns (if exists) - Read `.shaktra/memory/procedures.yml` — for workflow learnings (if exists) ### 2. Classify Intent Parse the user's request. Extract: - **Bug description** — the symptom being reported - **Error context** — stack traces, error messages, log snippets (if provided) - **Scope hints** — file paths, function names, component references ### 3. Dispatch Bug Diagnostician Spawn the bug-diagnostician agent for investigation: ``` Yo