Bug Review provides a disciplined loop for triaging and fixing bug reports one-by-one. For each report it mandates confirmation (reproduce/evidence), validation of proposed fixes (or push-back), explicit user agreement, test-driven implementation, and a summarized commit with changelog entry. It enforces single-commit-per-bug discipline and detailed verification gates.
Use when the user supplies one or more explicit bug reports and expects a review-style workflow with confirm-before-fix and per-bug commits. Not intended for quick ad-hoc debugging unless the user frames it as a review queue.
Fits developer-oriented agent providers that can run tests and edit code (e.g., Codex, Copilot-style implementations, agent runners with test execution).
Pure workflow/process skill with no scripts. Well-structured 5-phase bug review discipline: confirm, validate/push back, get agreement, implement TDD, commit with changelog. Clear anti-patterns section and relationship to other skills. Heavy project-specific references to CLAUDE.md, capsem_core, and just commands limit general applicability but demonstrate thorough thinking for its original context.
No scripts present — static analysis only. Skill is a well-crafted process/workflow document. The per-bug commit discipline and push-back-on-fixes approach are genuinely useful patterns. Security is perfect (nothing to exploit). Quality is strong but docked slightly for project-specific assumptions embedded in the instructions.