Audit Prep Assistant helps the owner of a codebase get it ready for outside assessors. It sets review goals, runs static analysis, raises test coverage, removes dead code, makes the code easy to build and read, and generates documentation.
The deliverable is a prep package: a goals document, a triaged static analysis report, a coverage report, a file scope list, build instructions, a frozen commit and a documentation set, tracked in a checklist.
What You Get
- A review goals document with objectives, areas of concern, worst-case scenario and questions for auditors
- A triaged static analysis report and a test coverage report with the untested paths named
- A scope list, verified build instructions and a frozen commit or branch
- Flowcharts, user stories, an actors and privileges map, function documentation and a glossary
- A prep checklist of completed and remaining items
Common Use Cases
- Preparing a Solidity protocol for an external audit
- Working out what to fix before auditors start
- Asking what assessors need from a project
- Cleaning up dead code and boilerplate before a review
What Makes It Unique
It encodes the preparation checklist of a security firm and applies it as a sequence that cannot be skipped. A table of rationalizations, such as a README being enough for setup or coverage that looks decent, maps each excuse to the action required. It is for the team being audited, and it points to audit-context-building for someone studying unfamiliar code.
Under The Hood
The skill is a single instruction file with no scripts and no declared tool list. It tells the agent to run static analysis commands such as slither, dylint and golangci-lint, and a coverage tool such as forge coverage, then edit the project to fix easy issues and write documentation files like architecture, user stories and glossary documents. It does not fetch web pages or call remote services.