report-regressions

$npx mdskill add trailofbits/skills/report-regressions

Input: frozen `scope.json`, campaign index, progress ledger, sealed stage packages and registry assignment. Follow [project guidance](../../references/evidence.md#project-guidance) for every scoped change before reporting.

SKILL.md

.github/skills/report-regressionsView on GitHub ↗
---
name: report-regressions
description: Use when assembling or refreshing an evidence-linked regression report from saved campaign decisions.
---

# Report a campaign

## When to Use

Input: frozen `scope.json`, campaign index, progress ledger, sealed stage packages
and registry assignment.
Follow [project guidance](../../references/evidence.md#project-guidance) for every scoped change before reporting.

## When NOT to Use

Adjudicating evidence or repairing records; return those needs to the caller.

## Report

1. Read the [standard](../../docs/regression-definition.md),
   [labels](../../docs/report-definitions.md) and
   [file contract](../../references/evidence.md). Reconcile the index against
   frozen scope, assigned changes and discovered candidates. Preserve PR/commit IDs and
   accepted duplicate mappings.
2. Run [report.py](../../scripts/report.py) via `uv run --no-project` with the campaign
   directory and `--output ASSIGNED_DIRECTORY/reports` to render HTML, Markdown and JSON.
   Exit 1 means changed evidence or an invalid index; return its diagnostics and record the stage as blocked. Exit 0 may include `UNRESOLVED` findings; report each `unresolved_reason` and the `verification` level of confirmed findings. Never repair decisions, invent
   evidence or edit hashes to pass validation.
3. Inspect counts and links. Preserve adjudicated outcomes/ratings. Separate
   incomplete fixes, latent/pre-existing bugs, rejected claims and unresolved
   work from confirmed totals.
4. Ensure reports include coverage gaps, setup/execution evidence, rating reasons
   and pending human review. Report missing information; do not claim completion
   while required content is absent.
   Seal `report-stage.json` with the assigned inputs and generated reports as artifacts;
   record validation failures as blocked.

## Report Back

Keep detailed findings in the reports. Return only:

- Status: `complete` or `blocked` for report production.
- Reports: sealed `report-stage.json` and validated output paths; identify incomplete outputs.
- Result: one sentence describing campaign coverage and unresolved work.
- Blocker: affected records, validation errors or required caller action.

A complete report may describe an incomplete campaign.

## Rationalizations to Reject

- “All agents finished”: that does not establish coverage or resolved candidates.

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.