magpie-issue-reassess-stats
Read-only dashboard over a directory of `verdict.json` files produced by `issue-reassess` campaigns. Surfaces a health rating, classification distribution, partial-fix surfaces, oldest-unresolved buckets, and per-component breakdowns. Output is HTML by default; markdown fallback available. Read-only on tracker state; consumes campaign artefacts.
apache · AI review on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add apache/magpie --skill magpie-issue-reassess-statsAbout this skill
SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0
name: magpie-issue-reassess-stats
family: issue
mode: Meta
description: |
Read-only dashboard over a directory of verdict.json files
produced by issue-reassess campaigns. Surfaces a health
rating, classification distribution, partial-fix surfaces,
oldest-unresolved buckets, and per-component breakdowns.
Output is HTML by default; markdown fallback available.
Read-only on tracker state; consumes campaign artefacts.
when_to_use: |
When a maintainer asks "what's the state of the reassessment
campaign", "give me the dashboard for the recent sweep", or
"which issues still fail across pool runs". Also as a
pre-release check on whether the EOL pool has dropped, and
as a periodic health-of-the-backlog view.
capability: capability:stats
license: Apache-2.0
issue-reassess-stats
Read-only dashboard skill over the verdict.json artefacts
produced by issue-reassess
campaigns. Surfaces a health rating, classification distribution,
the still-fails-* action tail, partial-fix surfaces, new-issue
candidates from cross-family probes, and per-component breakdowns.
The skill is the read-only counterpart to
issue-reassess — both consume the
same on-disk artefacts. Where reassess writes verdicts (one
per candidate) and a report.md, this skill renders an at-a-
glance dashboard for the maintainer to scan.
Modelled on pr-management-stats.
Golden rules
Golden rule 1 — read-only on tracker AND on campaign
artefacts. This skill reads verdict.json files and emits HTML.
It does not modify any campaign artefact, does not post to
<issue-tracker>, does not re-invoke issue-reproducer.
Golden rule 2 — HTML by default. The dashboard is designed for
the "what should I do today" glance. Markdown and tables-only
fallbacks are available for terminal pipelines (--markdown,
--tables-only).
Golden rule 3 — surface action candidates first. The dashboard opens with the still-failing-bug count and the new-issue candidates from probes — these are where work happens. The bulk fixed-on-master / cannot-run-* counts come second.
Golden rule 4 — fresh read on every invocation. The dashboard
re-reads verdict.json files on every run; no in-memory caching.
This makes the dashboard a coherent snapshot of the campaign
state at the moment of invocation.
Golden rule 5 — multi-campaign reads are explicit. When the user points the skill at a directory that contains multiple campaign subdirectories, it asks which one — never silently aggregates across campaigns.
Adopter overrides
Before running the default behaviour documented below, this skill
consults
.apache-magpie-local/issue-reassess-stats.md (personal, gitignored) and .apache-magpie-overrides/issue-reassess-stats.md (committed, project-wide)
in the adopter repo if it exists, and applies any agent-readable
overrides it finds. See
docs/setup/agentic-overrides.md
for the contract.
Hard rule: agents NEVER modify the snapshot under
<adopter-repo>/.apache-magpie/. Local modifications go in the
override file.
Snapshot drift
Also at the top of every run, this skill compares the gitignored
.apache-magpie.local.lock (per-machine fetch) against the
committed .apache-magpie.lock (the project pin). On mismatch
the skill surfaces the gap and proposes
/magpie-setup upgrade.
Prerequisites
- A campaign directory exists at the path the user supplies (or
the project's default per
<project-config>/reproducer-conventions.md). - That directory contains
<KEY>/verdict.jsonfiles for the campaign's candidates (at least one).
No tracker access required — the skill operates entirely on on-disk artefacts.
Inputs
| Selector | Resolves to |
|---|---|
stats <campaign-dir> (default) | path to a campaign directory |
--markdown | emit markdown instead of HTML |
--tables-only | emit terminal-rendered tables only (no hero cards, no recommendations) |
--output <file> | write to a file instead of stdout |
--component <name> | filter the dashboard to one component |
The default output is HTML to stdout; the user pipes it to a file or opens it directly.
Step 0 — Pre-flight
- Campaign directory exists at the supplied path.
- At least one
verdict.jsonpresent under the directory. - Override consultation — see Adopter overrides above.
- Drift check — see Snapshot drift above.
If the directory has multiple campaign subdirs (e.g., the user
pointed at <scratch>/), prompt which to use.
Step 1 — Fetch the verdicts
Read every verdict.json under the campaign directory. Parse and
schema-validate each per
issue-reproducer/verdict-composition.md.
Skip and report any file that fails to parse; do not aggregate
partial data.
Full details: fetch.md.
Step 2 — Classify
Bucket each verdict by classification (10 l