Skip to content
SkillModel-led458 tokens in use

report-regressions

The reporting stage of a regression-hunt campaign: turns sealed decisions into HTML, Markdown and JSON reports without repairing or inventing evidence.

8,320 stars on the repository CC-BY-SA-4.0trailofbits/skills · plugins/regression-hunt/skills/report-regressions
/plugin marketplace add trailofbits/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing report-regressions costs

20tokens idle
458tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure16/25
  • Examples3/15
  • Output10/15
  • Size10/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance52
  • Community64
  • Maturity32
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers