Menü
Predictive code analysis for identifying potential risks, anti-patterns, and future maintenance issues. Use when assessing code health or planning refactoring.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
| name | predictive-analysis |
| description | Predictive code analysis for identifying potential risks, anti-patterns, and future maintenance issues. Use when assessing code health or planning refactoring. |
| disable-model-invocation | false |
| user-invocable | true |
| allowed-tools | Read, Grep, Glob, Bash |
| argument-hint | ["target-path"] |
Analyzes codebases to proactively predict and identify risks that may become problems in the future.
The predictive code analysis system evaluates the following risk categories:
# Analyze entire project
/predictive-analysis
# Analyze a specific directory
/predictive-analysis src/
# Analyze by component
/predictive-analysis src/components/
| Level | Description | Response Deadline |
|---|---|---|
| Critical | Requires immediate fix, impacts production | Immediately |
| High | Requires urgent response, potential future failure | Within 1 week |
| Medium | Requires planned response, impacts maintainability | Within 1 month |
| Low | Improvement recommended, long-term quality | Next refactoring session |
Each risk is evaluated from the following perspectives:
The analysis classifies findings into the following categories:
Each prediction includes:
After analysis completes, you can choose from the following tracking methods:
"How would you like to track these predictions?"
1. Create Todos: Track resolution progress
2. Create GitHub Issues: Generate issues with detailed information
3. Summary only: Provide actionable report without creating tasks
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🔮 Predictive Code Analysis Report
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Critical] Security Risk
📍 Location: src/auth/login.ts:45-67
⚠️ Issue: User input concatenated into SQL string without input validation
📅 Timeline: Can be exploited immediately
💥 Impact: Risk of SQL injection attacks
🛠️ Mitigation: Use prepared statements or ORM
[High] Performance Bottleneck
📍 Location: src/api/search.ts:120-145
⚠️ Issue: O(n²) nested loop for data filtering
📅 Timeline: Latency occurs when data exceeds 1,000 records
💥 Impact: Response time over 10 seconds, degraded UX
🛠️ Mitigation: Switch to O(n) algorithm using Map/Set
For more detailed information, see:
Real-world usage examples:
This skill does NOT:
All suggestions are subject to human review and approval.
Route work in the `~/.apm` global APM workspace: decide what owns a change, which path is the source of truth, and which APM rollout / `mise` task to run. Use for skill update and redistribution requests (`skillアップデートして再配布して`, `再配布`), `apm.yml` / `apm.lock.yaml` and managed catalog rollout, manual-skills package state, orphaned APM packages, checked-out external dependency repositories, optional repository-scoped skill packages, and `apmのバージョンあげて` / pinned `apm` source checks. For skill body, description, script, reference, or asset design itself, coordinate with `skill-creator`; for general mise usage outside the APM workspace (including `mise upgrade TOOL` and `minimum_release_age`), use `mise`.
Use when deciding whether to install, enable, or troubleshoot Headroom context compression for local AI agent workflows, especially MCP, proxy, or agent-wrap usage.
Use when adding or reviewing CI-stability hooks and gates: Lefthook/pre-commit/pre-push configuration, aligning local push gates with GitHub Actions, deciding commit-vs-push gate scope, or migrating pre-commit to Lefthook. For mise task design itself, use `mise`; for debugging failing PR checks, use `gh-fix-ci`.
Curate external agent collections into this APM workspace. Use when evaluating whether an outside agent repository can be installed through APM, importing selected agents into catalog/agents, recording provenance, or refreshing curated agents from upstream.
Use when creating, rebuilding, or updating a Google Forms survey from a Markdown survey spec such as SURVEY_QUESTIONS.md, especially when the form should stay synchronized with question text, required flags, Google Forms item types, scale labels, and removed-question notes.
Slack app management knowledge for app settings, manifests, OAuth installs, scopes, bot users, Marketplace settings, App Home, display names, sender names, mrkdwn message formatting, and safe workspace-visible changes. Use when diagnosing or changing a Slack app, installed app, bot user, app label, DM header, chat sender, message text decoration, Slack links, block quotes, app approval/install state, token impact, Slack API app settings, Slack Marketplace settings, or stale Slack app name propagation.