| name | bug-review |
| description | Systematically uncover and fix bugs using language-specific expertise and
reproducible evidence.
Triggers: bug hunting, defect detection, debugging, fix verification, bug fix,
regression check, error investigation, defect documentation
Use when: deep bug hunting needed, documenting defects, verifying fixes,
systematic debugging required
DO NOT use when: test coverage audit - use test-review instead.
DO NOT use when: architecture issues - use architecture-review.
Use this skill for systematic bug hunting with evidence trails.
|
| category | code-review |
| tags | ["bugs","defects","debugging","code-quality","fixes","verification"] |
| tools | ["defect-tracker","fix-generator","verification-runner"] |
| usage_patterns | ["bug-hunting","defect-documentation","fix-preparation","verification-planning"] |
| complexity | intermediate |
| estimated_tokens | 450 |
| progressive_loading | true |
| dependencies | ["pensive:shared","imbue:evidence-logging","imbue:diff-analysis/modules/risk-assessment-framework"] |
Bug Review Workflow
Systematic bug identification and fixing with language-specific expertise.
Quick Start
/bug-review
When to Use
- Reviewing code for potential bugs
- After receiving bug reports
- Before major releases
- During security audits
- Investigating production issues
Required TodoWrite Items
bug-review:language-detectedbug-review:repro-planbug-review:defects-documentedbug-review:fixes-preparedbug-review:verification-plan
Progressive Loading
Load additional context as needed:
- Language Detection:
@include modules/language-detection.md - Manifest heuristics, expertise framing, version constraints
- Defect Documentation:
@include modules/defect-documentation.md - Severity classification, root cause analysis, static analyzers
- Fix Preparation:
@include modules/fix-preparation.md - Minimal patches, idiomatic patterns, test coverage
Workflow
Step 1: Detect Languages (bug-review:language-detected)
Identify dominant languages using manifest files (Cargo.toml → Rust, package.json → Node, etc.).
State expertise persona appropriate for the language ecosystem.
Note version constraints (MSRV, Python versions, Node engines).
Progressive: Load modules/language-detection.md for detailed manifest heuristics.
Step 2: Plan Reproduction (bug-review:repro-plan)
Identify reproduction methods:
- Unit/integration test suites
- Fuzzing tools
- Manual reproduction commands
Document exact commands:
cargo test -p core
pytest tests/test_api.py
npm test -- pkg
Capture blockers and propose mocks when dependencies unavailable.
Step 3: Document Defects (bug-review:defects-documented)
Review code line-by-line, logging each bug with:
