adjudicate-regression

$npx mdskill add trailofbits/skills/adjudicate-regression

Input: candidate, frozen sources, available reproduction/replay packages and registry assignment. Use a fresh context distinct from the reproducer and replayer. Early exclusions may lack experiments. Follow [project guidance](../../references/evidence.md#project-guidance) before target work.

SKILL.md

.github/skills/adjudicate-regressionView on GitHub ↗
---
name: adjudicate-regression
description: Use when deciding whether source and live reproduction evidence establish a new regression or an exclusion.
---

# Adjudicate evidence

## When to Use

Input: candidate, frozen sources, available reproduction/replay packages and
registry assignment. Use a fresh context distinct from the reproducer
and replayer. Early exclusions may lack experiments.
Follow [project guidance](../../references/evidence.md#project-guidance) before target work.

## When NOT to Use

Producing missing evidence; return the gap to the caller.

## Decide

1. Read the [standard](../../docs/regression-definition.md),
   [labels](../../docs/report-definitions.md) and
   [file contract](../../references/evidence.md). Verify seals. Inspect source,
   setup, PoC, actual logs and security assumptions, not only summaries.
2. Identify the claimed defect and assess whether the change introduced it. Rule out
   incomplete fixes, latent/pre-existing bugs, intentional changes, unsupported expectations
   and unreachable scenarios with cited evidence. Establish attacker access and applicable protections for
   security findings.
3. Confirm only when reproduction and independent replay ran the same PoC/input
   against live S0/S1 through real interfaces, showing correct behavior before and
   failure afterward. Explain supported behavior, reachability and patch causality.
   Assign severity/likelihood with reasons.
4. Otherwise select an evidenced exclusion or `UNRESOLVED`; state what remains
   unproved. For `UNRESOLVED`, put the standard's concise paragraph separating observed gaps,
   plausible explanations and resolving checks in `reason` so reports retain it.
   Incomplete fixes and existing bugs stay outside regression totals.
   Check known findings/issues/PRs before claiming novelty; report unknown if unavailable.
5. For requested deduplication, establish whether supplied candidates share a root
   cause. Preserve change mappings; never deduplicate unresolved claims into confirmation.
6. Write and seal `decision.json`; cite evidence for every conclusion.
   Record any blocker preventing adjudication.

## Report Back

Keep detailed reasoning in the sealed package. Return only:

- Status: `complete` or `blocked`, matching the record.
- Record: sealed `decision.json` path, or why none was produced.
- Result: outcome and one-sentence reason.
- Gap: missing evidence or required caller action, if any.

A completed decision may be `UNRESOLVED`; task status and finding outcome differ.

## Rationalizations to Reject

- “S0 passes and S1 fails”: exposing an existing defect is a latent bug.

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.
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.
c-reviewPerforms comprehensive C/C++ security review for memory corruption, integer overflows, race conditions, and platform-specific vulnerabilities. Use when auditing native C/C++ applications, reviewing daemons or services for memory safety, or hunting integer overflow / use-after-free / race conditions in userspace code.