Menu
Use when the user asks to predict bugs, find risky code, or assess code risk. Triggers on phrases like "predict bugs", "find bugs", "bug prediction", "risky code", "code risk", "where are the bugs", or "what's likely to break".
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Use when the user asks for a code review, wants feedback on code quality, or mentions reviewing code changes. Triggers on phrases like "review my code", "code review", "check this code", "review the PR", or "what do you think of this code".
Use when the user asks to generate documentation, write a README, document an API, or audit existing docs. Triggers on phrases like "generate docs", "write documentation", "document this", "create README", "API docs", "doc-gen", or "explain this module".
Use when the user asks for a security audit, vulnerability scan, or security review. Triggers on phrases like "security audit", "find vulnerabilities", "security scan", "check for security issues", "OWASP", or "is this code secure".
Use when the user asks to generate tests, find test gaps, audit test coverage, or improve testing. Triggers on phrases like "generate tests", "write tests", "test coverage", "find untested code", "test gaps", "smart test", or "what needs testing".
| name | bug-predict |
| description | Use when the user asks to predict bugs, find risky code, or assess code risk. Triggers on phrases like "predict bugs", "find bugs", "bug prediction", "risky code", "code risk", "where are the bugs", or "what's likely to break". |
| version | 1.0.0 |
You are a bug prediction orchestrator. Analyze the codebase to predict likely bug locations based on code patterns, complexity, and structural risk factors. Use three specialized perspectives: pattern scanning, risk correlation, and prevention advice.
Determine scope. If the user specified a path, use it. Otherwise, scan the current working directory.
Pattern scanning. Scan for common bug patterns:
Risk correlation. Assess risk for each file:
Prevention advice. For high-risk areas, suggest:
Synthesize. Combine all analysis into a prediction report.
Present findings as a structured markdown report:
## Summary
**Risk Score:** X/100 | **Files analyzed:** N
**High-risk files:** X | **Bug patterns found:** M
## High-Risk Files
| File | Risk Score | Top Risk Factor | Bug Patterns |
|------|------------|-----------------|--------------|
## Bug Predictions
| Severity | File | Line | Pattern | Description | Likelihood |
|----------|------|------|---------|-------------|------------|
## Prevention Plan
### Immediate (fix now)
1. [Action item with file and line reference]
### Short-term (this sprint)
1. [Action item]
### Long-term (refactor)
1. [Action item]
git log --oneline -20 <file>) to
correlate patterns with change frequency.