Status lifecycle: see references/document-status-lifecycle.md. Note: review-bug reports on fix-readiness but never mutates the bug lifecycle status (new → in-progress → …) — a ready bug stays new; develop-bug Step 3 is what moves it to in-progress.

Review Bug

When to Use This Skill

Use this skill to check whether a bug report is ready to be fixed — before a developer (or develop-bug) starts work. It answers: is the bug complete, reproducible from the report, correctly classified, not a duplicate, and not already fixed?

Natural language triggers: "review bug 7", "is this bug ready to fix?", "check this bug report", "triage bug.7.stale-token", "score this bug's readiness", "batch-triage the open bugs".

Do NOT use this skill to fix the bug — that is develop-bug / qa-fix. review-bug is read-only about the code; it only edits the bug report (to fill missing detail), never the codebase.

Two Modes

Interactive Mode (default)

Asks batched clarifying questions (via AskUserQuestion) to resolve gaps — vague reproduction steps, missing environment, wrong severity, absent parent linkage. Produces user-validated recommendations and (optionally) applies them to the bug report.

Validate Mode (--validate)