/audit
- Type:
/audit - What it does: Backend and architecture audit with proof — real tools, evidence per finding, report and plan
- In Spanish:
/auditar(when Senzu is installed with--lang es) - It is a shortcut: asking for it in plain words triggers the same thing through the router.
Usage: /audit [optional area, e.g. "payments", "public API" or "before production"] — the argument is optional unless stated otherwise; if none is given, the default behavior below applies.
Apply backend-audit §references/protocolo.md in full to whatever the user wrote after the command (or the whole backend):
- Scope: agree with the user, in one question, on the area and the goal (before refactoring, inheriting the project, an incident or going to production). If they don’t know, propose starting with the hotspots.
- Measurement: run
node <skills-dir>/backend-audit/scripts/hotspots.mjsand the stack tools (references/herramientas-por-stack.md) the project already has. Propose the missing ones; don’t install anything without asking. - Targeted reading of what the tools point to, going through
references/catalogo-hallazgos.md. - Verify each finding before reporting it: without evidence (output, file:line, failing test or measurement) it goes under suspicions, not findings. This task does NOT modify application code.
- Report with
references/informe.mdinsenzu/auditoria/<fecha>-<area>.md. Show the summary and the top 3-5 findings and ask what gets fixed. - What is approved → cards in
senzu/plan/PLAN.md(phase AU: «Para qué» (what for) = the finding, «Verificar» (verify) = the same evidence that proved it), worked through with/next; structural changes are made afterwards with/refactor. Devlog with the tools run and the result.
When finished
Section titled “When finished”With the AU cards approved in the plan: /next to work through them one by one (the structural ones, with /refactor).