variant analysis
- Repo stars 0
- Author updated Aug 24, 2026, 11:09 PM
- Author repo skills
- Domain
- Other
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @trailofbits · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- Python
- Detected file/system behavior
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# Variant Analysis
Find the other instances of a bug you have already found. One root cause usually has several
manifestations, and they are rarely in the module where you found the first one.
## When to Use
- A vulnerability has been found and you need to search for similar instances
- Building or refining CodeQL/Semgrep queries for security patterns
- Performing systematic code audits after an initial issue discovery
- Analyzing how a single root cause manifests in different code paths
## When NOT to Use
- Initial vulnerability discovery — use audit-context-building or a domain-specific audit
- General code review with no known pattern to search for
- Writing fix recommendations — use issue-writer
- Understanding unfamiliar code — use audit-context-building first
## The Five Steps
Read the reference for a step when you reach it.
**1. Understand the original issue.** Extract the root cause — why the code is wrong, not
what it does — and enumerate the directions a variant could hide in: related identifiers,
other manifestations of the same mistake, data-type edge cases.
→ [references/root-cause.md](references/root-cause.md)
**2. Create an exact match.** Write a pattern matching ONLY the known instance and confirm
it hits. A pattern that matches nothing means you have misunderstood the bug, and every
search built on it is calibrated against the wrong code.
**3–4. Generalize one element at a time.** Climb from the exact match toward the pattern
family, running and reading all matches after each single change. Stop when more than half
the matches are noise.
→ [references/searching.md](references/searching.md) — abstraction ladder, tool selection,
false-positive filters
**5. Triage.** Decide which candidates are real, and say so with a severity attached.
→ [references/triage.md](references/triage.md)
**Then write it up**, including the patterns that failed and a CI rule to prevent regression.
→ [references/reporting.md](references/reporting.md)
## Running it as a Workflow
This plugin ships `/variant-analysis:variants`, which runs the five steps across parallel
subagents — one per expansion axis, looping until the sweep stops finding anything new.
Each stage reads the reference above that matches its job.
Use the workflow when the codebase is large or the root cause has many manifestations. Work
the steps directly when the search is narrow or you want a say in each generalization.
## What Makes Hunts Fail
1. **Narrow scope** — searching only the module the original bug was in
2. **Pattern too specific** — searching one attribute and missing the family around it
3. **One vulnerability class** — chasing a single manifestation of the root cause
4. **Happy-path testing** — never trying the null, empty, and boundary cases
5. **Generalizing too fast** — abstracting several elements at once, so noise cannot be
attributed to any one of them
The first three are covered in root-cause.md and searching.md, the fourth in triage.md.
## Resources
**CodeQL** (`resources/codeql/`): `python.ql`, `javascript.ql`, `java.ql`, `go.ql`, `cpp.ql`
**Semgrep** (`resources/semgrep/`): `python.yaml`, `javascript.yaml`, `java.yaml`, `go.yaml`, `cpp.yaml`
**Report**: `resources/variant-report-template.md`
Sections and files
Listed in source order.
sections -> When to Use → When NOT to Use → The Five Steps → Running it as a Workflow → What Makes Hunts Fail → Resources
terms -> 1. Understand the original issue. · 2. Create an exact match. · 3–4. Generalize one element at a time. · 5. Triage. · Then write it up · Narrow scope · Pattern too specific · One vulnerability class
files/cmd -> /variant-analysis:variants · resources/codeql/ · python.ql · javascript.ql · java.ql · go.ql · cpp.ql · resources/semgrep/
body sha256 -> 3af0066a939a
When to Use
A vulnerability has been found and you need to search for similar instances Building or refining CodeQL/Semgrep queries for security patterns Performing systematic code audits after an initial issue discovery Analyzing how a single root cause manifests in different code paths
When NOT to Use
Initial vulnerability discovery — use audit-context-building or a domain-specific audit General code review with no known pattern to search for Writing fix recommendations — use issue-writer Understanding unfamiliar code — use audit-context-building first
The Five Steps
Read the reference for a step when you reach it. 1. Understand the original issue. Extract the root cause — why the code is wrong, not what it does — and enumerate the directions a variant could hide in: related identifiers, other manifestations of the same mistake, data-type edge cases. → references/root-cause.md
Running it as a Workflow
This plugin ships
/variant-analysis:variants, which runs the five steps across parallel subagents — one per expansion axis, looping until the sweep stops finding anything new. Each stage reads the reference above that matches its job. Use the workflow when the codebase is large or the root cause has many manifestations. Work the steps directly when the search is narrow or you want a say in each generalization.What Makes Hunts Fail
Narrow scope — searching only the module the original bug was in Pattern too specific — searching one attribute and missing the family around it One vulnerability class — chasing a single manifestation of the root cause Happy-path testing — never trying the null, empty, and boundary cases Generalizing too fast — abstracting several elements at once, so noise cannot be