audit-reporting
Structured finding format: severity, impact, PoC, remediation. Templates and classification standards for audit output. Used by Report Compiler.
- License 许可
- MIT
- 最近更新
- 2026-10-18
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- audit-reporting
- description
- Structured finding format: severity, impact, PoC, remediation. Templates and classification standards for audit output. Used by Report Compiler.
03 SKILL.md 正文
Audit Reporting Skill
Purpose
Ensure all audit outputs follow a consistent, auditor-grade format with proper severity classification, concrete impact descriptions, and traceable evidence chains.
Severity Classification (Immunefi Standard)
| Severity | Criteria |
|---|---|
| Critical | Direct loss of funds, permanent freezing of funds, protocol insolvency |
| High | Theft of unclaimed yield, permanent DoS, governance manipulation |
| Medium | Griefing with material loss, temporary DoS, value extraction below threshold |
| Low | Non-critical issues, informational findings, gas optimizations |
Finding Report Structure
Every confirmed finding must include:
- Title: One-line description
- Severity: Critical/High/Medium/Low with justification
- Impact: Concrete description (e.g., "Attacker can drain 100% of vault TVL")
- Root Cause: Specific code flaw with file and line reference
- Attack Path: Step-by-step, numbered sequence
- PoC: Link to runnable Foundry test
- Affected Code: File, lines, snippet
- Remediation: Specific fix with code example
Evidence Chain
Every finding must have a traceable path:
Task (specs/tasks/TASK-{N}.md)
→ Reasoning (specs/reasoning/TASK-{N}-reasoning.md)
→ Verification (specs/verification/TASK-{N}-verification.md)
→ Finding (findings/FINDING-{ID}.md)
What Makes a Finding Actionable
- ❌ "There may be a reentrancy risk" — NOT actionable
- ✅ "Reentrancy in Vault.withdraw() allows attacker to drain all ETH. PoC at test/exploit.t.sol" — actionable
Coverage Reporting
The coverage map must honestly distinguish:
- Full coverage: Function analyzed with multiple task approaches
- Partial coverage: Function analyzed but not all paths/values tested
- No coverage: Function not targeted by any task (must be in gap record)
04 同仓库更多 Skills
stripe-patterns
暂无简介
payment-patterns
暂无简介
testing-patterns
Testing patterns for Jest and Playwright. Use when writing tests, setting up test fixtures, or validating RLS enforcement. Routes to existing test conventions.
team-coordination
Agent Teams orchestration patterns for multi-agent SAFe workflows. Use when spawning agent teams, coordinating teammates, enforcing quality gates via task dependencies, or orchestrating the 11-agent SAFe pipeline. Covers team creation, messaging, shared task lists, and SAFe gate enforcement. Do NOT use for single-agent or simple subagent workflows.
task-compilation
Compile broad audit goals into structured proof obligations with 9 mandatory fields. Used after decomposition by the Threat Modeler agent.
storage-layout-analysis
Proxy patterns, slot collisions, upgrade safety. Used during decomposition to identify storage-related vulnerabilities in upgradeable contracts.