メニュー
Hunts bugs with evidence trails. Use when investigating unexpected behavior or before merging code with potential hidden defects.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Detects AI-generated writing patterns in prose. Use when reviewing docs for slop, vague language, or identity leaks before publishing.
Audits Rust code for unsafe blocks, ownership issues, and Cargo dependency risks. Use when reviewing Rust code or before merging Rust changes.
Recommends context compression strategies for bloated or quota-heavy sessions. Use when context feels sluggish or quota burns faster than expected.
Guide minimal code via a decision ladder with full safety, edge, and negative-case coverage. Use when adding code, choosing a dependency, or auditing a diff.
Optimizes context window via MECW principles and memory tiering. Use when context exceeds 30% or before long multi-step tasks.
Generates or remediates documentation with human-quality writing. Use when creating new docs, rewriting AI-generated content, or applying style profiles.
| name | bug-review |
| role | library |
| description | Hunts bugs with evidence trails. Use when investigating unexpected behavior or before merging code with potential hidden defects. |
| alwaysApply | false |
| category | code-review |
| tags | ["bugs","defects","debugging","code-quality","fixes","verification"] |
| tools | [] |
| usage_patterns | ["bug-hunting","defect-documentation","fix-preparation","verification-planning"] |
| complexity | intermediate |
| model_hint | standard |
| estimated_tokens | 450 |
| progressive_loading | true |
| dependencies | ["pensive:shared","imbue:proof-of-work","imbue:diff-analysis/modules/risk-assessment-framework","imbue:review-core","imbue:structured-output"] |
| modules | ["modules/defect-documentation.md","modules/fix-preparation.md","modules/language-detection.md"] |
bug-review:language-detected)bug-review:repro-plan)bug-review:defects-documented)bug-review:fixes-prepared)bug-review:verification-plan)Systematic bug identification and fixing with language-specific expertise.
/bug-review
Verification: Run the command with --help flag to verify availability.
bug-review:language-detectedbug-review:repro-planbug-review:defects-documentedbug-review:fixes-preparedbug-review:verification-planbug-review:findings-verifiedLoad 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
Verification: Run pytest -v tests/test_api.py to verify.
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:proof-of-work 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.
bug-review:findings-verified)Every defect must cite a real file:line and a verbatim Anchor. Write
findings to .review/findings.json and confirm each citation resolves:
python plugins/imbue/scripts/citation_verifier.py \
--findings .review/findings.json --repo-root .
Drop or label UNVERIFIED any defect the verifier fails (exit 1); only
verified defects enter the report. See Skill(imbue:review-core) Step 5
for the protocol and Skill(imbue:structured-output) for the schema.
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
- Anchor: `verbatim source text at file.rs:142`
- 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
Verification: Run pytest -v to verify tests pass.
file:line + verbatim Anchor, and citation_verifier.py confirmed all citations (exit 0) or unverified defects were dropped or labeled UNVERIFIED