メニュー
Analyze Rust code for performance issues, allocation hot spots, and optimization opportunities
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Write-then-verify documentation pipeline. Use when a user asks to improve comments or docs, explain algorithms or design choices, write or upgrade docstrings, or raise documentation quality for a codebase (especially Rust crates). Writes docs, then automatically verifies every claim against code reality using a fresh agent to eliminate confirmation bias.
Use when you have code review findings, PR comments, or review reports that need to be systematically addressed — especially when there are multiple findings across different files and severities
Use when creating any beads task — auto-researches the codebase, links related tasks, and produces a rich self-contained description from a structured template. Accepts minimal intent and outputs a complete task ready for agent implementation.
Use when you have code review findings, PR comments, or review reports that need to be systematically addressed — especially when there are multiple findings across different files and severities
Use when a task needs an implementation plan that is iteratively created and stress-tested through review-and-revise cycles before implementation begins — catches blind spots, incorrect codebase assumptions, unnecessary complexity, and performance pitfalls while changes are still cheap
Use when a markdown plan file exists and needs validation before implementation — catches design flaws, logic holes, footguns, unnecessary complexity, and performance concerns while changes are still cheap
| name | performance-analyzer |
| description | Analyze Rust code for performance issues, allocation hot spots, and optimization opportunities |
Analyze performance-critical code in this secret scanning engine.
src/engine/ modulessrc/stdx/with_capacity() for known-size collections#[inline(always)] on hot functionsstd::mem::size_of)Arc when Rc or ownership would workget_unchecked with proof)&str vs String in function signaturesThis codebase uses these performance patterns:
NONE_U32 = u32::MAX as sentinel (avoid Option overhead)#[inline(always)] on hot-path functionsdebug_assert! for invariant checks (zero cost in release)G) for compile-time granularity selection## Performance Analysis: [file/function]
### Findings
| Severity | Issue | Location | Impact |
|----------|-------|----------|--------|
| HIGH | Allocation in hot loop | line:XX | ~Xns per call |
| MEDIUM | Missing inline hint | line:XX | Potential call overhead |
### Recommendations
1. **[Issue]**: [Specific fix with code example]
```rust
// Before
// After
Run these benchmarks to verify:
cargo bench --bench <relevant_bench>
## Related Skills
- `bench-compare` - Before/after measurement
- `rust-hotspot-finder` - Systematic hotspot scanning
- `perf-regression` - Full regression workflow