audit-context-building

Analyze codebase functions to map assumptions, guarantees, and cross-function dependencies before security audits.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/mewishu/awesome-skills --skill audit-context-building-mewishu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-context-building
Source: https://github.com/mewishu/awesome-skills/tree/main/skills/pattern/thinking-framework/audit-context-building
Command: npx skills add https://github.com/mewishu/awesome-skills --skill audit-context-building-mewishu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security audits and architecture reviews often fail because reviewers hunt for bugs before understanding how the system fits together, producing findings nobody can judge. This Skill builds a structured model of unfamiliar code first, recording what each function assumes, guarantees, and depends on. ## Core Features & Use Cases - Per-Function Analysis: Dispatches subagents to analyze each function, recording inputs, trust levels, preconditions, effects, and block-by-block reasoning with line citations. - Unenforced Assumption Detection: Flags assumptions marked "nothing found" where code relies on a condition nothing establishes, the most valuable input for the vulnerability-hunting phase. - Cross-Domain Support: Covers smart contracts, C/C++, decompiled firmware, and web services with domain-specific guidance on trust boundaries and black-box calls. - Use Case: Starting a smart contract audit, run the skill on the repository to produce a dossier mapping every function's invariants and couplings, then hand the unenforced assumptions and open questions to the hunting phase. ## Quick Start Run the audit-context-building skill on this codebase to map each function's assumptions, guarantees, and dependencies before I start looking for vulnerabilities.

Frequently Asked Questions about audit-context-building

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

FAQPage Schema
How do I understand an unfamiliar codebase before a security audit?

Run this skill on the codebase path to dispatch per-function analysis subagents that produce a dossier of assumptions, guarantees, and dependencies. It records what each function takes on faith and flags assumptions nothing enforces, giving the audit phase a verified system model.

What is the difference between audit context building and vulnerability hunting?

Context building maps what code assumes and guarantees without naming vulnerabilities, rating severity, or proposing fixes. Vulnerability hunting is a separate later phase that consumes the dossier's unenforced assumptions and open questions to make those judgments.

Does this audit approach work for smart contracts and firmware?

Yes, the analysis format is language-neutral and domain notes cover smart contracts, C/C++, decompiled firmware, and web services. Each domain maps its own trust boundaries, persistent state, and black-box call types, such as unresolved decompiler symbols or external contract addresses.

How are black-box external calls handled during analysis?

Calls to code outside the project, like unknown contract addresses or unresolved binary symbols, are recorded with what is passed, what is assumed, and what outcomes are not excluded. A bound never established in visible code is marked as an assumption with nothing found.

When should I not use audit context building?

Skip it on code you already understand well, since the token cost is not justified. It is also the wrong tool when you want immediate vulnerability findings, severity ratings, or fixes, as those belong to the hunting phase that follows.