AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

report-regressions

Use when assembling or refreshing an evidence-linked regression report from saved campaign decisions.

Original source
trailofbits
License
CC-BY-SA-4.0
Pinned revision
2be6433b39e009cd2b6fd3be1895f6b1faa5af9a

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read trailofbits--report-regressions at revision 2be6433b39e009cd2b6fd3be1895f6b1faa5af9a, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 1

SKILL.md

Report a campaign

When to Use

Input: frozen scope.json, campaign index, progress ledger, sealed stage packages and registry assignment. Follow 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, labels and file contract. Reconcile the index against frozen scope, assigned changes and discovered candidates. Preserve PR/commit IDs and accepted duplicate mappings.
  2. Run 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.