← ClaudeAtlas

auditlisted

Router running the audits of the current project - asks which ones to trigger (checklist - bugs/UB, quality/conventions, dependencies licenses + vulnerabilities, tests coverage, performance - coverage and benchmark checked and run automatically) and the report format, then runs the selected audit skills one after the other and writes a summary report linking them. Invoke manually with /audit.
TsukiNi22/ai-utils · ★ 1 · Testing & QA · score 77
Install: claude install-skill TsukiNi22/ai-utils
# Audit router **Request given with `/audit`:** $ARGUMENTS Load the skills with the Skill tool (never the other routers: they are manual-only). Never start fork agents; an audit that offers parallel agents asks the user first (its own rule). ## 1. Context - Project root: `git rev-parse --show-toplevel` (or the current folder outside a repository), languages / build system, `git log --oneline -1` (the commit audited). - Output folder: `audit/` at that root (created if missing), never `docs/` unless asked. ## 2. Ask (one AskUserQuestion call, French questions) 1. **Quels audits lancer ?** (`multiSelect: true`, all checked = recommended): - `Bugs / UB` -> `audit-bugs` (sanitizers, tests, review; slow on big projects) - `Sécurité / failles` -> `audit-security` (memory errors, injection, auth, secrets, network...: fixed in passes until a clean one; its report is always a PDF) - `Propreté / conventions` -> `audit-quality` - `Dépendances` -> `audit-deps` (licenses to credit / restrictive, known vulnerabilities, transitive) - `Légal / conformité` -> `legal-check` (GDPR, cookies, legal notice, terms, accessibility, licenses, mentions; its scope global / web asked by it) - `Couverture des tests` -> `coverage` (C++ with tests: measured with llvm-cov) or `tests` (other languages) - `Performance` -> `benchmark` (profiling of the main scenario of the project) 2. **Format du rendu**: `Markdown + PDF (Recommandé)` · `PDF seulement` · `Markdown seulement` (pass