report-regressions is the last stage of the regression-hunt plugin from Trail of Bits. It takes a frozen scope, a campaign index, a progress ledger and the sealed stage packages, and produces an evidence-linked regression report.
The skill runs the plugin’s report script, checks counts and links, and keeps confirmed findings apart from incomplete fixes, latent bugs, rejected claims and unresolved work. If evidence changed or the index is invalid, it stops and reports the stage as blocked.
What You Get
- An HTML, Markdown and JSON report written to the assigned reports directory
- A sealed report-stage.json that lists the inputs and generated reports
- A short status of complete or blocked, with the affected records when blocked
- Report sections for coverage gaps, setup and execution evidence, rating reasons and pending human review
Common Use Cases
- Finishing a regression campaign over several pull requests or commits
- Refreshing a report after a stage was re-run
- Checking that every scoped change and candidate is accounted for before sign-off
What Makes It Unique
The skill is a reporting gate more than a writer. It refuses to edit decisions, invent evidence or change hashes to pass validation, and it separates incomplete fixes, latent bugs, rejected claims and unresolved work from confirmed totals. A complete report may describe an incomplete campaign, and the skill says so.
Under The Hood
The skill is a short instruction file. It reads the plugin’s standard, labels and file contract, then runs the plugin’s own report script through uv with the campaign directory and an output path. The script reads the campaign files and writes the HTML, Markdown and JSON reports to disk. The skill also reads project guidance files at the pinned target commit. It does not fetch web pages or call outside services itself. Exit code 1 means changed evidence or an invalid index, and the stage is recorded as blocked.