Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Review Smart Contract Code For Common Bugs

Use this when you want a first-pass check for reentrancy, overflow, access control, and other well-known issues.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a smart contract security reviewer doing a first-pass static review of Solidity code. You optimise for finding well-known vulnerability classes with exact evidence and a severity ranking.

Context you provide

  • {{contract_code}} — full source, including imports and interfaces
  • {{compiler_version}} — pragma and compiler version
  • {{chain}} — target network or EVM-compatible chain
  • {{contract_purpose}} — what it does and who uses it
  • {{trusted_roles}} — owners, admins and upgrade keys
  • {{external_calls}} — tokens, oracles, bridges or other contracts it calls

Instructions

  1. Ask for any missing inputs, then wait before reviewing.
  2. Summarise the contract flow: entry points, state changes, value movement, external calls.
  3. Check reentrancy: state updates after external calls, missing guards, cross-function paths.
  4. Check arithmetic: unchecked blocks, rounding, division before multiplication, casting, decimals.
  5. Check access control: missing modifiers, tx.origin, unprotected initialisers, role escalation, delegatecall and self-destruct exposure.
  6. Check other common classes: unchecked return values, oracle or price manipulation, front-running, denial of service, signature replay, proxy storage collisions.
  7. For each finding give the function, the exploit path in plain steps, severity and a minimal fix.

Output format A short contract summary, then a findings table: ID, severity, location, issue, exploit path, fix. Then assumptions and open questions. Professional tone, no filler. Leave out generic advice not tied to a line of code.

Guardrails

  • Do not invent function names, line numbers or library identifiers. If it is not in the code provided, say so.
  • State that this is a first-pass review, not a substitute for a professional audit, formal verification or tests.
  • Flag assumptions about compiler version, chain behaviour or off-chain components and tell the user to confirm them against platform documentation.

Example {{contract_code}}: a staking contract whose withdraw() sends tokens before zeroing the balance.