Variant Analysis Skill

Hunt for vulnerability variants across the entire codebase using root-cause patterns.

56|9|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/0x-Shashi/WEB3-AUDIT-SKILLS --skill variant-analysis-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Variant Analysis Skill
Source: https://github.com/0x-Shashi/WEB3-AUDIT-SKILLS/tree/main/skills/variant-analysis
Command: npx skills add https://github.com/0x-Shashi/WEB3-AUDIT-SKILLS --skill variant-analysis-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically hunt for every variant of a discovered vulnerability across the entire codebase.

Core Features & Use Cases

  • Abstract vulnerabilities to root-cause patterns to enable cross-file discovery.
  • Drive comprehensive variant searches across all contracts and modules in a project.
  • Expand findings to related patterns and cross-contract variants for full coverage.
  • Integrate with existing audit workflows to maximize finding counts and reduce blind spots.

Quick Start

Document the initial finding, abstract to a root-cause pattern, and run a variant hunt across the codebase to enumerate all related instances.

Frequently Asked Questions about Variant Analysis Skill

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

FAQPage Schema
How do I find all instances of a vulnerability pattern across a codebase?

Variant analysis is the process of abstracting a discovered vulnerability into a root-cause pattern and systematically searching the entire codebase to identify all matching instances. It ensures comprehensive coverage by validating and expanding findings to related cross-contract patterns.

What is the best way to identify root-cause variants in smart contracts?

The best way to identify root-cause variants is to abstract a discovered vulnerability into a root-cause pattern and execute a multi-step variant hunt across the codebase. This systematically validates and expands findings to related patterns for full cross-contract coverage.

Can variant analysis be used for competitive audit workflows like Code4rena or Sherlock?

Yes, variant analysis is explicitly designed for competitive audit workflows like Code4rena or Sherlock. It drives comprehensive variant searches across contracts and modules, expanding findings to related patterns to maximize finding counts and reduce blind spots.

What do I need to start a variant hunt across my codebase?

To start a variant hunt across your codebase, you need an initial documented finding. You then abstract this finding to a root-cause pattern and run a multi-step variant hunt to enumerate, validate, and expand all related code instances.

Why does my codebase audit miss related vulnerabilities sharing the same root cause?

Audits miss related vulnerabilities when findings are not abstracted to root-cause patterns. By systematically hunting for variants and expanding findings to related cross-contract patterns, you reduce blind spots and ensure all instances of the same root-cause are identified.