issue-reassess-stats

Name: issue-reassess-stats
Author: apache

68stars52forks

How to install issue-reassess-stats?

apache/magpie/issue-reassess-stats

$npx -y skills add apache/magpie --skill issue-reassess-stats

Installs into the current project.

Summary

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

Files · 1

View on GitHub

SKILL.md

1	<!-- SPDX-License-Identifier: Apache-2.0
2	https://www.apache.org/licenses/LICENSE-2.0 -->
3
4	<!-- Placeholder convention (see ../../AGENTS.md#placeholder-convention-used-in-skill-files):
5	<project-config> → adopter's project-config directory
6	<issue-tracker> → URL of the project's general-issue tracker
7	<issue-tracker-project> → project key within the tracker
8	<upstream> → adopter's public source repo
9	<default-branch> → upstream's default branch
10	Substitute these with concrete values from the adopting
11	project's <project-config>/ before running any command below. -->
12
13	# issue-reassess-stats
14
15	Read-only dashboard skill over the `verdict.json` artefacts
16	produced by [`issue-reassess`](../issue-reassess/SKILL.md)
17	campaigns. Surfaces a health rating, classification distribution,
18	the `still-fails-*` action tail, partial-fix surfaces, new-issue
19	candidates from cross-family probes, and per-component breakdowns.
20
21	The skill is the read-only counterpart to
22	[`issue-reassess`](../issue-reassess/SKILL.md) — both consume the
23	same on-disk artefacts. Where reassess writes verdicts (one
24	per candidate) and a `report.md`, this skill renders an at-a-
25	glance dashboard for the maintainer to scan.
26
27	Modelled on [`pr-management-stats`](../pr-management-stats/SKILL.md).
28
29	---
30
31	## Golden rules
32
33	**Golden rule 1 — read-only on tracker AND on campaign
34	artefacts.** This skill reads `verdict.json` files and emits HTML.
35	It does not modify any campaign artefact, does not post to
36	`<issue-tracker>`, does not re-invoke `issue-reproducer`.
37
38	Golden rule 2 — HTML by default. The dashboard is designed for
39	the "what should I do today" glance. Markdown and tables-only
40	fallbacks are available for terminal pipelines (`--markdown`,
41	`--tables-only`).
42
43	Golden rule 3 — surface action candidates first. The dashboard
44	opens with the still-failing-bug count and the new-issue
45	candidates from probes — these are where work happens. The bulk
46	fixed-on-master / cannot-run-* counts come second.
47
48	Golden rule 4 — fresh read on every invocation. The dashboard
49	re-reads `verdict.json` files on every run; no in-memory caching.
50	This makes the dashboard a coherent snapshot of the campaign
51	state at the moment of invocation.
52
53	Golden rule 5 — multi-campaign reads are explicit. When the
54	user points the skill at a directory that contains multiple
55	campaign subdirectories, it asks which one — never silently
56	aggregates across campaigns.
57
58	---
59
60	## Adopter overrides
61
62	Before running the default behaviour documented below, this skill
63	consults
64	[`.apache-magpie-local/issue-reassess-stats.md`](../../docs/setup/agentic-overrides.md) (personal, gitignored) and [`.apache-magpie-overrides/issue-reassess-stats.md`](../../docs/setup/agentic-overrides.md) (committed, project-wide)
65	in the adopter repo if it exists, and applies any agent-readable
66	overrides it finds. See
67	[`docs/setup/agentic-overrides.md`](../../docs/setup/agentic-overrides.md)
68	for the contract.
69
70	Hard rule: agents NEVER modify the snapshot under
71	`<adopter-repo>/.apache-magpie/`. Local modifications go in the
72	override file.
73
74	---
75
76	## Snapshot drift
77
78	Also at the top of every run, this skill compares the gitignored
79	`.apache-magpie.local.lock` (per-machine fetch) against the
80	committed `.apache-magpie.lock` (the project pin). On mismatch
81	the skill surfaces the gap and proposes
82	[`/magpie-setup upgrade`](../setup/upgrade.md).
83
84	---
85
86	## Prerequisites
87
88	- A campaign directory exists at the path the user supplies (or
89	the project's default per
90	[`<project-config>/reproducer-conventions.md`](../../projects/_template/reproducer-conventions.md)).
91	- That directory contains `<KEY>/verdict.json` files for the
92	campaign's candidates (at least one).
93
94	No tracker access required — the skill operates entirely on
95	on-disk artefacts.
96
97	---
98
99	## Inputs
100
101	\| Selector \| Resolves to \|
102	\|---\|---\|
103	\| `stats <campaign-dir>` (default) \| path to a campaign directory \|
104	\| `--markdown` \| emit markdown instead of HTML \|
105	\| `--tables-only` \| emit terminal-rendered tables only (no hero cards, no recommend

People who liked this also viewed

6 picks

Type

issue-reassess-stats

68stars52forks

View on GitHub

How to install issue-reassess-stats?

apache/magpie/issue-reassess-stats

$npx -y skills add apache/magpie --skill issue-reassess-stats

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	<!-- SPDX-License-Identifier: Apache-2.0
2	https://www.apache.org/licenses/LICENSE-2.0 -->
3
4	<!-- Placeholder convention (see ../../AGENTS.md#placeholder-convention-used-in-skill-files):
5	<project-config> → adopter's project-config directory
6	<issue-tracker> → URL of the project's general-issue tracker
7	<issue-tracker-project> → project key within the tracker
8	<upstream> → adopter's public source repo
9	<default-branch> → upstream's default branch
10	Substitute these with concrete values from the adopting
11	project's <project-config>/ before running any command below. -->
12
13	# issue-reassess-stats
14
15	Read-only dashboard skill over the `verdict.json` artefacts
16	produced by [`issue-reassess`](../issue-reassess/SKILL.md)
17	campaigns. Surfaces a health rating, classification distribution,
18	the `still-fails-*` action tail, partial-fix surfaces, new-issue
19	candidates from cross-family probes, and per-component breakdowns.
20
21	The skill is the read-only counterpart to
22	[`issue-reassess`](../issue-reassess/SKILL.md) — both consume the
23	same on-disk artefacts. Where reassess writes verdicts (one
24	per candidate) and a `report.md`, this skill renders an at-a-
25	glance dashboard for the maintainer to scan.
26
27	Modelled on [`pr-management-stats`](../pr-management-stats/SKILL.md).
28
29	---
30
31	## Golden rules
32
33	**Golden rule 1 — read-only on tracker AND on campaign
34	artefacts.** This skill reads `verdict.json` files and emits HTML.
35	It does not modify any campaign artefact, does not post to
36	`<issue-tracker>`, does not re-invoke `issue-reproducer`.
37
38	Golden rule 2 — HTML by default. The dashboard is designed for
39	the "what should I do today" glance. Markdown and tables-only
40	fallbacks are available for terminal pipelines (`--markdown`,
41	`--tables-only`).
42
43	Golden rule 3 — surface action candidates first. The dashboard
44	opens with the still-failing-bug count and the new-issue
45	candidates from probes — these are where work happens. The bulk
46	fixed-on-master / cannot-run-* counts come second.
47
48	Golden rule 4 — fresh read on every invocation. The dashboard
49	re-reads `verdict.json` files on every run; no in-memory caching.
50	This makes the dashboard a coherent snapshot of the campaign
51	state at the moment of invocation.
52
53	Golden rule 5 — multi-campaign reads are explicit. When the
54	user points the skill at a directory that contains multiple
55	campaign subdirectories, it asks which one — never silently
56	aggregates across campaigns.
57
58	---
59
60	## Adopter overrides
61
62	Before running the default behaviour documented below, this skill
63	consults
64	[`.apache-magpie-local/issue-reassess-stats.md`](../../docs/setup/agentic-overrides.md) (personal, gitignored) and [`.apache-magpie-overrides/issue-reassess-stats.md`](../../docs/setup/agentic-overrides.md) (committed, project-wide)
65	in the adopter repo if it exists, and applies any agent-readable
66	overrides it finds. See
67	[`docs/setup/agentic-overrides.md`](../../docs/setup/agentic-overrides.md)
68	for the contract.
69
70	Hard rule: agents NEVER modify the snapshot under
71	`<adopter-repo>/.apache-magpie/`. Local modifications go in the
72	override file.
73
74	---
75
76	## Snapshot drift
77
78	Also at the top of every run, this skill compares the gitignored
79	`.apache-magpie.local.lock` (per-machine fetch) against the
80	committed `.apache-magpie.lock` (the project pin). On mismatch
81	the skill surfaces the gap and proposes
82	[`/magpie-setup upgrade`](../setup/upgrade.md).
83
84	---
85
86	## Prerequisites
87
88	- A campaign directory exists at the path the user supplies (or
89	the project's default per
90	[`<project-config>/reproducer-conventions.md`](../../projects/_template/reproducer-conventions.md)).
91	- That directory contains `<KEY>/verdict.json` files for the
92	campaign's candidates (at least one).
93
94	No tracker access required — the skill operates entirely on
95	on-disk artefacts.
96
97	---
98
99	## Inputs
100
101	\| Selector \| Resolves to \|
102	\|---\|---\|
103	\| `stats <campaign-dir>` (default) \| path to a campaign directory \|
104	\| `--markdown` \| emit markdown instead of HTML \|
105	\| `--tables-only` \| emit terminal-rendered tables only (no hero cards, no recommend

People who liked this also viewed

6 picks

Type