← ClaudeAtlas

execute-auditlisted

Run a current aidd audit against a local project, preserving reports under .aidd/audit-reports/ and actionable findings as .aidd/features/audit-*. Use to run a named aidd audit against a project and capture its findings.
NomadicDaddy/aidd · ★ 1 · AI & Automation · score 60
Install: claude install-skill NomadicDaddy/aidd
# Execute Audit Run an aidd audit against a local project through audit mode, preserving reports under `.aidd/audit-reports/` and actionable findings as `.aidd/features/audit-*`. ## Usage ``` execute-audit <app> <audit-name> execute-audit <app> --audit-all ``` ## Arguments - `<app>` - Target app from `<applications-root>/AGENTS.md` or an explicit path containing `.aidd/`. - `<audit-name>` - Audit definition name from `<aidd-root>/audits/`, without `.md`. - `--audit-all` - Run the applicable audit set through aidd's profile-aware audit selection. ## Workflow 1. Resolve the app to a local directory and verify `.aidd/` exists. Stop for external or unmapped targets. 2. Verify the requested audit exists under `<aidd-root>/audits/`. If no audit was supplied, run all applicable audits in filename order using the current audit-all flags. 3. Run from `<aidd-root>`: ```bash bun run start -- --project-dir <app-dir> --audit <AUDIT_NAME> ``` For an applicable batch, use the current aidd audit-all flags rather than manually concatenating audit files. 4. Let aidd persist the report and findings. Do not hand-write `.aidd/audit-reports/`, `.aidd/features/`, or `.aidd/CHANGELOG.md` outside the aidd audit result contract. 5. After the run, inspect the summary and generated paths. Expected outputs are: - `.aidd/audit-reports/<AUDIT_NAME>-<timestamp>.md`; - zero or more `.aidd/features/audit-*` feature directories. 6. If new feature files were created, read th