bug-investigationlisted

Root-cause investigation workflow for unexpected behavior, test failures, performance regressions, data inconsistencies, and cross-layer data-flow tracing. Use when users ask to investigate or trace a bug, regression, flaky test, or root cause (including 測試失敗、效能異常、調查 Bug、追蹤資料流). Not for direct implementation when the root cause is already confirmed, ordinary code review, or pure feature work. Output: a phase-based evidence report, confirmed root cause or explicit blocked state, solution options, stop-loss state, and next actions.
hmj1026/dhpk · ★ 2 · Data & Documents · score 68

Install: claude install-skill hmj1026/dhpk

# Bug Investigation Skill ## Overview Use a five-phase evidence loop to move from symptom to root cause, then to a bounded repair handoff: `Clarify → Gather evidence → Trace and confirm → Design the fix → Preserve knowledge` Keep the investigation record current. Every conclusion must point to evidence; every unresolved claim must be labelled as a hypothesis or blocker. ## When NOT to Use - Root cause is confirmed and the user wants implementation: hand off to `dhpk:bug-fix`. - The task is ordinary code or document review: use the relevant review skill. - The task is pure feature development with no failure, regression, or inconsistency: use `adaptive-dev-workflow` / `feature-dev`. ## Core Contract 1. Complete all five phases. If a phase is blocked, record the missing evidence, blocker, and next action in the investigation document before stopping. 2. Do not propose a fix or edit production code until Phase 3 has a confirmed root cause and a minimal verification result. 3. Preserve raw logs, code, query, field, and test names; write explanations and documents in Traditional Chinese unless the project requires another language. 4. Follow the repository's `AGENTS.md`, `CLAUDE.md`, and execution-policy SSOT before choosing tools, artifacts, or OpenSpec routing. In dhpk-style repositories this means reading `rules/execution-policy.md` "Change classification & OpenSpec routing (SSOT)" and explicitly selecting either OpenSpec (`/opsx:new`) or a brief-plan handoff; OpenSpec