메뉴
Investigate bugs automatically - error logs, code paths, root cause analysis, edge cases. Trigger when user types /forge-bug-investigate or requests bug investigation/debugging.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Review AI/LLM integrations - client configurations, prompt quality, and fallback safety. Trigger when user types /forge-ai-audit or requests an AI audit/review.
Review project architecture - patterns, separation, modularity, SOLID. Trigger when user types /forge-architecture-review or requests an architecture review.
Review database usage - queries, indexing, schema, migrations. Trigger when user types /forge-database-review or requests a database review.
Review project dependencies - outdated, unused, licenses, supply chain risks. Trigger when user types /forge-dependency-review or requests a dependency review.
Audit application performance - queries, memory, algorithms, caching, resources. Trigger when user types /forge-performance-audit or requests a performance audit/review.
Pre-release checklist - changelog, version, CI/CD, breaking changes. Trigger when user types /forge-release-check or requests a pre-release check.
| name | forge-bug-investigate |
| description | Investigate bugs automatically - error logs, code paths, root cause analysis, edge cases. Trigger when user types /forge-bug-investigate or requests bug investigation/debugging. |
Investigate bugs automatically using AI reasoning.
/forge-bug-investigate [path] [--quick|--deep] [--markdown|--json] [--verbose]
[path] — Target directory (default: current directory)--quick — Fast scan, focus on critical issues only--deep — Thorough scan, check all patterns--markdown — Output as markdown (default)--json — Output as JSON--verbose — Include detailed evidenceAnalyze source code for:
Use shared/analyzer/ to detect:
Execute analysis prompts:
prompts/error-log-analysis.md)prompts/code-path-tracing.md)prompts/root-cause-analysis.md)prompts/edge-case-detection.md)For each finding:
Use shared/report/ to generate:
Follow the markdown report format generated by shared/report/markdown.ts. It MUST use the following layout:
Project: [Project Name]
Path: [Project Path]
Language: [Primary Language]
Framework: [Detected Framework (optional)]
Date: [Timestamp]
[Score]/100 (Grade: [Grade])
| Severity | Count |
|---|---|
| 🔴 Critical | [count] |
| 🟠 High | [count] |
| 🟡 Medium | [count] |
| 🔵 Low | [count] |
| ⚪ Info | [count] |
Found [total] issues: [count] critical, [count] high, [count] medium, [count] low, [count] info.
| Title | Location | Description | Impact |
|---|---|---|---|
| [Finding Title] | [file-name]:[line] | [Description] | [Impact] |
[code snippet]