hunt-regressions

$npx mdskill add trailofbits/skills/hunt-regressions

Input: sealed preparation, frozen S0/S1, change context and registry assignment. On retry, include this assignment's prior candidate-ID mapping. The caller supplies these, including for independent use. Follow [project guidance](../../references/evidence.md#project-guidance) before target work.

SKILL.md

.github/skills/hunt-regressionsView on GitHub ↗
---
name: hunt-regressions
description: Use when discovering possible regressions from a pinned change and its callers before reproduction.
---

# Discover candidates

## When to Use

Input: sealed preparation, frozen S0/S1, change context and registry assignment.
On retry, include this assignment's prior candidate-ID mapping. The caller supplies
these, including for independent use.
Follow [project guidance](../../references/evidence.md#project-guidance) before target work.

## When NOT to Use

Proving a known candidate; use reproduction. Discovery cannot confirm findings.

## Hunt

1. Read the [standard](../../docs/regression-definition.md) and
   [file contract](../../references/evidence.md). Verify preparation; read frozen
   change messages, PR discussion and security documentation for intent and supported use.
2. Review the entire diff; trace changed behavior through callers to real interfaces.
   Use frozen sources and supplied context, not later fixes, advisories or other reviews.
3. Record each lead's changed code, previously supported behavior, reachable trigger,
   proposed new defect, false-positive checks and required proof. Retain supplied
   leads suggesting old bugs or incomplete fixes for adjudication.
   Leave PoC construction to reproduction.
4. Reserve each lead's ID through [registry.py](../../scripts/registry.py) `candidate`
   using its stable hypothesis key and assigned agent handle. Reuse the key on retry.
   Write candidate files and `hunt.json` with IDs, file mappings, coverage and limitations.
   An empty list is valid.
   If blocked, record partial coverage and uninspected areas. Seal the package.

## Report Back

Keep detailed evidence in the sealed package. Return only:

- Status: `complete` or `blocked`, matching the record.
- Record: sealed `hunt.json` path, or why none was produced.
- Result: candidate count and material coverage gaps.
- Blocker: missing prerequisite or required caller action, if blocked.

## Rationalizations to Reject

- “A helper fails on invented input”: show a supported interface that reaches it.

More from trailofbits/skills

SkillDescription
address-sanitizerBuilds and runs code under AddressSanitizer to catch buffer overflows, use-after-free, and other memory errors during fuzzing or tests. Covers -fsanitize=address builds, ASAN_OPTIONS, reading the crash report, LeakSanitizer, and the overhead and platform trade-offs. Use when fuzzing C/C++ or Rust that has unsafe blocks or FFI, when debugging a memory corruption crash, or when reading an ASan stack trace.
adjudicate-regressionUse when deciding whether source and live reproduction evidence establish a new regression or an exclusion.
aflppSets up and runs AFL++ for multi-core fuzzing of C/C++ projects built with afl-clang-fast or afl-gcc-fast. Covers instrumentation modes, parallel main and secondary campaigns, persistent mode, corpus minimization, and crash triage. Use when scaling fuzzing across cores, fuzzing a mature C/C++ codebase, reading the afl-fuzz status screen, or moving on after libFuzzer has plateaued.
agentic-actions-auditorAudits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches AI agents running in CI/CD pipelines, including env var intermediary patterns, direct expression injection, dangerous sandbox configurations, and wildcard user allowlists. Use when reviewing workflow files that invoke AI coding agents, auditing CI/CD pipeline security for prompt injection risks, or evaluating agentic action configurations.
algorand-vulnerability-scannerScans Algorand smart contracts for 11 common vulnerabilities including rekeying attacks, unchecked transaction fees, missing field validations, and access control issues. Use when auditing Algorand projects (TEAL/PyTeal).
atherisSets up and runs Atheris, the coverage-guided Python fuzzer built on libFuzzer. Covers TestOneInput harnesses, FuzzedDataProvider, instrumenting both pure Python and native C extensions, and running under AddressSanitizer. Use when fuzzing a Python package, hunting memory corruption in a Python C extension, or choosing between Atheris and Hypothesis for a Python target.
audit-augmentation>
audit-context-buildingUnderstand a codebase before looking for bugs in it - what each function assumes, what it guarantees, and what it depends on elsewhere. Use when starting an audit, threat model, or architecture review on unfamiliar code, and before any vulnerability-hunting pass.
audit-prep-assistantPrepares codebases for security review using Trail of Bits' checklist. Helps set review goals, runs static analysis tools, increases test coverage, removes dead code, ensures accessibility, and generates documentation (flowcharts, user stories, inline comments). Use when preparing your own codebase to be audited by someone else, getting a repository review-ready before an external security review, deciding what to fix before auditors start, or asking what assessors need from a project. For understanding unfamiliar code you are about to audit, use audit-context-building instead.
burpsuite-project-parserSearches and explores Burp Suite project files (.burp) from the command line. Use when searching response headers or bodies with regex patterns, extracting security audit findings, dumping proxy history or site map data, or analyzing HTTP traffic captured in a Burp project.