메뉴
Audit a codebase read-only across seven quality pillars into one ranked report. Use when the user wants to assess, health-check, or audit a codebase or one pillar. Not for fixing findings, reviewing a change, or checking a feature works.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Initialize or refresh the project memory bank. Use when the user wants to set up or regenerate the project's memory files. Not for updating one memory file after it exists or editing a single rule directly.
Guide a project's journey through AIDD, from first setup to shipping a feature. Use when the user says onboard me, where do I start, or what to do next. Not for listing every installed surface.
Design and validate a new SaaS's architecture into an INSTALL.md via Q&A and stack comparison. Use when the user starts a project, chooses a stack, or picks an architecture pattern. Not for editing an existing stack or scaffolding code.
Route a request to generate a context artifact (skill, rule, agent, command, or hook) to its generator when the kind is unnamed. A named kind triggers its generator directly. Not for listing existing artifacts.
Generate a router-based skill across the host AI tools a project uses. Use when the user wants to create, scaffold, or refactor a skill, or turn a workflow into one. Not for other artifacts like rules, agents, commands, hooks.
Generate a coding rule that governs editor and agent behavior across the host AI tools. Use when the user wants to write, add, or refactor a rule, convention, or coding standard. Not for other artifacts like skills, agents, or hooks.
| name | 04-audit |
| description | Audit a codebase read-only across seven quality pillars into one ranked report. Use when the user wants to assess, health-check, or audit a codebase or one pillar. Not for fixing findings, reviewing a change, or checking a feature works. |
| argument-hint | code-quality | architecture | security | dependencies | performance | tests | ui |
| model | opus |
Diagnose a codebase against quality pillars and emit one ranked findings report. Read-only: it identifies and ranks problems, never changes code.
| # | Action | Pillar | Lens |
|---|---|---|---|
| 01 | code-quality | code-quality | Clean code (naming, SOLID, DRY, readability, smells) and tech debt (dead code, complexity, file/function size, error handling) |
| 02 | architecture | architecture | Conformance to C4 / ADRs, coupling, boundaries, layering |
| 03 | security | security | OWASP risks, authz, input validation, secrets in code |
| 04 | dependencies | dependencies | CVEs, licenses, outdated and unused deps, supply chain |
| 05 | performance | performance | N+1 queries, hot paths, bundle size, heavy operations |
| 06 | tests | tests | Critical-path coverage, flakiness, test pyramid balance |
| 07 | ui | ui | Loading/error/empty states, visual hierarchy, design-system drift, responsive, a11y |
Run the one pillar named, or offer all seven when the request is unscoped.
Before running an action, read its file in actions/, not only the table or assets.
aidd_docs/tasks/<yyyy_mm>/<yyyy_mm_dd>_audit/, like a feature folder. Every pillar that runs always writes its own <pillar>.md there, alone or in a full run. A full run additionally writes a merged report.md: one Findings table (category = pillar, severity-first), one Top-actions list, and one Coverage section over all seven pillars.Coverage > Skipped with the reason, and never invent findings for it.file:line, the issue, a suggested fix, and an effort.assets/audit-template.md: the report structure both run modes fill.