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.
/plugin marketplace add athola/claude-night-market/plugin install parseltongue@claude-night-marketThis skill inherits all available tools. When active, it can use any tool Claude has access to.
modules/defect-documentation.mdmodules/fix-preparation.mdmodules/language-detection.mdSystematic bug identification and fixing with language-specific expertise.
/bug-review
bug-review:language-detectedbug-review:repro-planbug-review:defects-documentedbug-review:fixes-preparedbug-review:verification-planLoad additional context as needed:
@include modules/language-detection.md - Manifest heuristics, expertise framing, version constraints@include modules/defect-documentation.md - Severity classification, root cause analysis, static analyzers@include modules/fix-preparation.md - Minimal patches, idiomatic patterns, test coveragebug-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.
bug-review:repro-plan)Identify reproduction methods:
Document exact commands:
cargo test -p core
pytest tests/test_api.py
npm test -- pkg
Capture blockers and propose mocks when dependencies unavailable.
bug-review:defects-documented)Review code line-by-line, logging each bug with:
Run static analyzers (cargo clippy, ruff check, golangci-lint, eslint).
Use imbue:evidence-logging for reproducible capture.
Progressive: Load modules/defect-documentation.md for classification details and analyzer commands.
bug-review:fixes-prepared)Draft minimal, idiomatic patches using language best practices:
Create tests following Red → Green pattern:
Progressive: Load modules/fix-preparation.md for language-specific patterns and test strategies.
bug-review:verification-plan)Execute reproduction steps with fixes applied.
Capture evidence:
Document remaining risks using imbue:diff-analysis/modules/risk-assessment-framework.
Assign owners and deadlines for follow-up items.
Severity: Critical (crash/data loss) → High (broken features) → Medium (degraded UX) → Low (edge cases)
Root Causes: Logic errors | API misuse | Concurrency issues | Resource leaks | Validation gaps
## Summary
[Brief scope description]
## Defects Found
### [D1] file.rs:142 - Title
- Severity: High
- Root Cause: Logic error
- Impact: Data corruption possible
- Fix: [description]
## Proposed Fixes
### Fix for D1
[code diff with explanation]
## Test Updates
[new/updated tests with Red → Green verification]
## Evidence
- Commands executed
- Logs and outputs
- External references
Build robust backtesting systems for trading strategies with proper handling of look-ahead bias, survivorship bias, and transaction costs. Use when developing trading algorithms, validating strategies, or building backtesting infrastructure.