Skip to content
SkillModel-led507 tokens in use

adjudicate-regression

The decision stage of regression-hunt: weigh source and live evidence, then confirm a regression or record why a candidate is excluded or unresolved.

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

Install command as written in the repository's README

Skill label

measured from its files

What installing adjudicate-regression costs

23tokens idle
507tokens 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

Nothing detected: no shell, network, file writes, git or credentials in its files.

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
  • Output15/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

Adjudicate-regression takes a candidate, frozen sources, any reproduction and replay packages, and a registry assignment, and decides whether a change introduced a defect. It runs in a fresh context apart from the reproducer and the replayer.

The agent inspects source, setup, PoC and actual logs, rules out incomplete fixes, latent bugs, intentional changes and unreachable scenarios, and confirms only when the same PoC failed after the change and passed before, through real interfaces. The result is a sealed decision record.

What You Get

  • A sealed decision.json that cites evidence for each conclusion
  • An outcome of confirmed, an evidenced exclusion or unresolved, with a concise reason
  • A statement of what remains unproved when the result is unresolved
  • A short report back with status, record path, result and any gap

Common Use Cases

  • Deciding whether a reproduced failure was introduced by a given change
  • Separating regressions from latent bugs and incomplete fixes
  • Checking whether candidate findings share one root cause

What Makes It Unique

A defect that passes before and fails after is not enough: exposing an existing defect counts as a latent bug. Confirmation needs the same PoC replayed independently against live before and after states, and unresolved claims are never merged into confirmed ones.

Under The Hood

The agent reads SKILL.md plus a regression definition, report definitions and an evidence file contract in the plugin, then inspects sealed packages, logs and sources. It checks known findings, issues and pull requests for novelty when it can reach them, and writes a sealed JSON decision into the campaign directory. The skill ships no scripts of its own and runs no target code, because reproduction is another stage.

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