القائمة
Audit AI-generated apps for security, performance, and maintainability issues. Use when user says /vibe-audit or "I generated this with AI and want to know how bad it is".
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Plan before executing. Use when task touches 3+ files, requires new folder structure, involves DB or API changes, or has step dependencies. Waits for approval before writing code.
Structured debugging workflow — diagnose before proposing fixes. Use when user says /debug, reports a bug, an error, or unexpected behavior. Forms hypotheses before touching code.
Compact the current conversation into a handoff document for a fresh agent to continue the work.
Manage persistent memory across sessions. Subcommands: save [topic] captures session learnings, recall [question] retrieves relevant context before acting, clean removes stale entries.
Review code with real engineering criteria — logic bugs, security vulnerabilities, and technical debt. Use when user says /review @file or /review to review current PR changes.
Generate a semantic commit message by reading the real staged diff. Use when the user says /commit, "make a commit", or "commit the changes". Never invents — reads the actual diff.
| name | ak:vibe-audit |
| description | Audit AI-generated apps for security, performance, and maintainability issues. Use when user says /vibe-audit or "I generated this with AI and want to know how bad it is". |
| disable-model-invocation | true |
| argument-hint | [@folder or leave empty for current project] |
| context | fork |
| agent | Explore |
Audit of apps built with vibe coding. Detects the typical problems AI generated without anyone reviewing them: security, performance, maintainability, and accumulated technical debt.
$ARGUMENTS
If Target is empty, audit the current project root. If a folder path is provided, scope the audit to that folder only.
When the user writes /vibe-audit or /vibe-audit @folder.
Also useful when someone says "I generated this with AI and want to know how bad it is".
See patterns.md for the complete list of patterns — what to look for, the risk, and the fix for each one. Load it before starting the audit.
# Vibe Audit — [project name]
Audited: [date]
## Summary
- 🔴 Critical: N (block production or are security risks)
- 🟡 Important: N (affect stability or maintainability)
- 🔵 Improvements: N (technical debt, quality)
---
## 🔴 Critical
### [Problem name]
**Where:** `path/file.ts` line X
**Evidence:**
[problematic code]
**Risk:** [what can happen if not fixed]
**Suggested fix:**
[corrected code or concrete steps]
---
## 🟡 Important
[same format]
---
## 🔵 Improvements
[same format]
---
## What's good
[1-3 things vibe coding did well — balanced feedback is more actionable]
## Suggested action plan
1. [This first — the most urgent critical]
2. [Then this]
3. [...]