workflow-engineer-analyze-buglisted

Diagnose one kind:bug issue read-only: reproduce it (browser MCP first, Playwright fallback, both against a booted stack), root-cause it to file:line, and post a `# Bug Analysis` comment proposing the fix + regression-test plan, then flip status → ready-to-review for a human to approve. Writes NO production code, creates NO branch, opens NO PR. Activate when dispatched with `Analyze bug #<n>` or '/workflow-engineer-analyze-bug'.
MartinKChen/harness-claude-code · ★ 0 · AI & Automation · score 72

Install: claude install-skill MartinKChen/harness-claude-code

# workflow-engineer-analyze-bug The **front half** of the bug lifecycle: turn a reporter's symptom (the bug issue body, Zone A) into an approved, actionable fix plan. Dispatched by the unified implement command's analyze stage for a freshly-filed `kind:bug` issue (carries `kind:bug`, no `status:*`). This step is **diagnosis only** — it reproduces, root-causes, and proposes; it writes no production code, creates no fix branch, and opens no PR. The human approves the proposed approach (by flipping a label) before any code is written, and the automatic `fix-bug` workflow does the actual regression-test + fix afterward. Keeping analyze read-only is what makes the human approval gate meaningful: nothing has been built yet. ## When to activate - The dispatch prompt opens with `Analyze bug #<n>`. - The user types `/workflow-engineer-analyze-bug`, or "analyze / triage / diagnose bug #<n>". Do NOT activate to write the fix (that is `workflow-engineer-fix-bug`, post-approval), to fix a PR, or for slice work. ## Input contract Read the bug issue #<n> body — the reporter's symptom (`operation-git/templates/bug-issue.md` shape): Summary, Environment, Steps to reproduce, Expected vs. actual, Evidence, Severity, Regression anchor. The Steps to reproduce + Evidence are your starting point for reproduction; the Environment (app version / commit) anchors where to look. ## Workflow ### 1. Read the bug body + light context Fetch the issue via `bash skills/operation-git/scripts/issue-bo