audit

Run a post-change audit that enumerates all created, modified, and deleted files using git diff or session logs, then reads each file to confirm the content matches intent. The audit flags leftover TODO markers, placeholder data, and broken references in a structured report.

Check each Markdown file's frontmatter against your tree's conventions doc for required fields such as type, created, modified, and tags. The audit also verifies tags come from the approved list and that language fields are set for bilingual content.

No, the audit only reports issues and does not fix them unless the user explicitly asks. It acts as an independent reviewer, treating the work as if someone else did it, and outputs a report with severity levels and an overall verdict.

The report lists every reviewed file with an OK, Warning, or Error status, details each issue with severity, and ends with an overall PASS, PASS WITH WARNINGS, or FAIL summary. It can be saved to a dated health report file in your notes tree.

Run it after any major implementation, multi-file refactor, or batch of note changes, or whenever you ask an agent to verify what was done. It is most valuable when the scope of changes is large enough that manual review would miss inconsistencies.