What problem does it solve? Security audits are more effective when the codebase arrives well-prepared, but teams often hand auditors messy code with missing documentation, stale static analysis results, and unclear scope. This Skill walks you through Trail of Bits' preparation checklist so auditors can focus on real vulnerabilities instead of setup friction. ## Core Features & Use Cases - Static Analysis & Cleanup: Runs platform-appropriate tools (Slither for Solidity, dylint for Rust, golangci-lint for Go, CodeQL/Semgrep) and helps triage findings, raise test coverage, and remove dead code. - Accessibility Package: Produces scoped file lists, verified build instructions, frozen commit/branch identification, and boilerplate attribution. - Documentation Generation: Creates flowcharts, sequence diagrams, user stories, actor/privilege maps, glossaries, and NatSpec-style function documentation. - Use Case: Two weeks before a Trail of Bits review of your Solidity DeFi protocol, use this Skill to run Slither, push coverage above 80%, freeze an audit branch, and generate the full documentation package to hand to the assessment team. ## Quick Start Ask the assistant to prepare your repository for an upcoming security audit by running static analysis, checking test coverage, and generating the audit documentation package.
