general-audit

Audit Solidity smart contracts against a multi-section security checklist.

1|1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/Apegurus/solidity-argus --skill general-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: general-audit
Source: https://github.com/Apegurus/solidity-argus/tree/main/skills/checklists/general-audit
Command: npx skills add https://github.com/Apegurus/solidity-argus --skill general-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a detailed checklist to systematically identify and mitigate security vulnerabilities in Solidity smart contracts, ensuring robust and safe code.

Core Features & Use Cases

  • Extensive Coverage: Spans critical areas like Access Control, Reentrancy, Arithmetic, Oracles, and more.
  • Standardized References: Includes SWC IDs and custom checklist items for thorough review.
  • Use Case: A smart contract developer can use this checklist during their code review process to ensure all common and advanced security pitfalls are considered before deployment.

Quick Start

Use the general-audit skill to review the attached contract 'VaultContract.sol' against the provided checklist.

Frequently Asked Questions about general-audit

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

FAQPage Schema
How do I audit a Solidity smart contract for security vulnerabilities?

To audit a Solidity smart contract for security vulnerabilities, use a comprehensive multi-section checklist covering access control, reentrancy, arithmetic, external calls, and oracles. This approach systematically identifies common and advanced security pitfalls using SWC IDs before deployment.

What security checks are needed for Solidity smart contracts before deployment?

Required security checks for Solidity smart contracts include reviewing access control, reentrancy, arithmetic, external calls, token handling, oracles, state management, DoS, frontrunning, governance, upgradeability, cryptography, gas efficiency, and code quality to ensure robust and safe code.

How do I use a checklist to identify reentrancy and access control issues in Solidity?

To identify reentrancy and access control issues in Solidity, apply a structured checklist that cross-references SWC IDs and custom security checks during your code review process, ensuring systematic vulnerability identification across critical attack vectors.

Does this smart contract audit checklist cover oracle manipulation and frontrunning?

Yes, this smart contract audit checklist covers oracle manipulation and frontrunning, alongside other critical areas like governance, upgradeability, and gas efficiency, providing a thorough review process to mitigate these specific security vulnerabilities.

Can I use this security checklist for complex Solidity contracts with upgradeability features?

Yes, you can use this security checklist for complex Solidity contracts because it explicitly includes an upgradeability section, along with governance and cryptography checks, ensuring robust security reviews for advanced contract architectures.

What is the best way to systematically review Solidity code for DoS and state management vulnerabilities?

The best way to systematically review Solidity code for DoS and state management vulnerabilities is to follow a standardized checklist referencing SWC IDs, ensuring all potential denial of service and state manipulation pitfalls are methodically evaluated.