Audit Context Building Skill

To build pre-audit context, systematically map the architecture, identify privileged roles, trace token flows, and document invariants to prevent missed edge cases during the deep code review.

The best way to map multi-contract architectures is creating a contract inventory that documents inheritance, interactions, and external dependencies to guide the security audit.

Identify centralization risks by performing a role and trust analysis to map privileged roles and evaluate trust assumptions across the protocol's multi-contract architecture.

Documenting protocol invariants and value flows is needed to align assumptions and trace token movements accurately, preventing missed edge cases during the deep code review.

Yes, you can evaluate unfamiliar DeFi protocols by executing a pre-audit context workflow to capture documentation, define scope, and map dependencies before reviewing code.

Starting without pre-audit context mapping leads to misaligned assumptions and missed edge cases, as protocol invariants, role discovery, and value flows remain undocumented.