| name | forge-performance-audit |
| description | Audit application performance - queries, memory, algorithms, caching, resources. Trigger when user types /forge-performance-audit or requests a performance audit/review.
|
/forge-performance-audit
Audit application performance using AI reasoning.
Command
/forge-performance-audit [path] [--quick|--deep] [--markdown|--json] [--verbose]
Options
[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 evidence
Purpose
Analyze source code for:
- N+1 query patterns
- Memory leaks
- Algorithm complexity issues
- Missing caching opportunities
- Resource usage problems
Workflow
Step 1: Understand Project
Use shared/analyzer/ to detect:
- Repository type
- Primary language
- Framework
- Database usage
Step 2: Run Performance Analysis
Execute analysis prompts:
- Query Analysis (
prompts/query-analysis.md)
- Memory Analysis (
prompts/memory-analysis.md)
- Algorithm Analysis (
prompts/algorithm-analysis.md)
- Caching Review (
prompts/caching-review.md)
- Resource Usage (
prompts/resource-usage.md)
Step 3: Generate Report
Use shared/report/ to generate:
- Performance Score (0-100)
- Bottleneck analysis
- Optimization recommendations
Output Format
Follow the markdown report format generated by shared/report/markdown.ts. It MUST use the following layout:
Performance Audit Report
Project: [Project Name]
Path: [Project Path]
Language: [Primary Language]
Framework: [Detected Framework (optional)]
Date: [Timestamp]
Score
[Score]/100 (Grade: [Grade])
| Severity | Count |
|---|
| 🔴 Critical | [count] |
| 🟠 High | [count] |
| 🟡 Medium | [count] |
| 🔵 Low | [count] |
| ⚪ Info | [count] |
Executive Summary
Found [total] issues: [count] critical, [count] high, [count] medium, [count] low, [count] info.
🔍 Detailed Findings
[Severity Group (e.g. 🔴 Critical)]
| Title | Location | Description | Impact |
|---|
| [Finding Title] | [file-name]:[line] | [Description] | [Impact] |
📂 Code Evidence
Finding #[number]: [Finding Title]
[code snippet]
