audit-prep-assistant

Prepare codebases for security reviews using static analysis and documentation.

Updated Jan 30, 2026

Search Tags:#static analysis #code review #documentation #security audit #test coverage #smart contracts

Ready to run

npx skills add https://github.com/andrescardonas7/salchipapa-web --skill audit-prep-assistant-andrescardonas7

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: audit-prep-assistant
Source: https://github.com/andrescardonas7/salchipapa-web/tree/main/.cursor/skills/audit-prep-assistant
Command: npx skills add https://github.com/andrescardonas7/salchipapa-web --skill audit-prep-assistant-andrescardonas7

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of preparing a codebase for a security audit, ensuring all necessary documentation, checks, and cleanups are completed to make the audit process smoother and more effective.

Core Features & Use Cases

Security Audit Preparation: Guides users through a checklist based on Trail of Bits' recommendations.
Codebase Analysis: Runs static analysis tools, checks test coverage, and identifies dead code.
Documentation Generation: Assists in creating flowcharts, user stories, and comprehensive documentation.
Use Case: A development team is two weeks away from a critical security audit. They use this Skill to systematically prepare their smart contract codebase, ensuring all documentation is up-to-date, static analysis reports are clean, and a stable version is frozen for the auditors.

Quick Start

Use the audit-prep-assistant skill to help prepare the current project for a security audit.

Frequently Asked Questions about audit-prep-assistant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prepare my smart contracts for a security audit?▼

Preparing a codebase for a security audit involves running static analysis tools like Slither and Semgrep, increasing test coverage, removing dead code, and generating comprehensive documentation such as flowcharts and user stories to ensure code accessibility.

What static analysis tools should I run before a codebase security review?▼

Before a security review, you should run static analysis tools including Slither and Dylint for Solidity and Rust, alongside Golangci-lint, CodeQL, and Semgrep to identify vulnerabilities and ensure the codebase meets security baseline requirements.

Does audit preparation support Rust and Go codebases or only Solidity smart contracts?▼

Audit preparation adapts to different platforms including Solidity, Rust, and Go. It runs platform-specific static analysis tools like Dylint for Rust and Golangci-lint for Go, alongside general tools like Semgrep and CodeQL.

How do I document code accessibility for auditors?▼

To document code accessibility for auditors, generate comprehensive documentation that includes build instructions, flowcharts, user stories, and a glossary. This ensures auditors can easily navigate and understand the codebase during the security review.

Why remove dead code before a smart contract security audit?▼

Removing dead code before a security audit reduces the attack surface and allows auditors to focus on active execution paths. This streamlines the review process by ensuring static analysis tools report only relevant vulnerabilities.