issues-refresh

Étoiles12

Forks5

Mis à jour26 juillet 2026 à 12:03

Sweep the whole board and re-triage it — re-derive every non-Done issue's fields, correct drift, split what has outgrown itself, close what no longer deserves to exist, and promote what is now shaped. A long, high-reasoning periodic pass. Use to audit a board that has grown untrustworthy, after a batch of merges, or when a milestone ships.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

exit-zero-labs

exit-zero-labs/threat-forge

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Spécialistes en gestion de projetsProfessions des affaires et des opérations financières·SOC 13-1082

SKILL.md

readonly

name	issues-refresh
description	Sweep the whole board and re-triage it — re-derive every non-Done issue's fields, correct drift, split what has outgrown itself, close what no longer deserves to exist, and promote what is now shaped. A long, high-reasoning periodic pass. Use to audit a board that has grown untrustworthy, after a batch of merges, or when a milestone ships.

Refresh the board

issue-triage shapes one issue. This re-derives the whole board, because shaping goes stale: milestones ship, dependencies merge, surfaces get refactored, and an issue triaged two months ago describes a repository that no longer exists.

Guardrails

Re-derive, never rubber-stamp. Decide each field as if seeing the issue fresh. A sweep that confirms everything it looks at has not audited anything.
Do not churn what is already right. Record an issue as verified and move on. Rewriting a correct description to look busy costs review attention and buries the changes that matter.

Procedure

Establish the ground truth first: current main, every open pull request, and which milestones have shipped. Drift is measured against reality, not against the last sweep.
Pull every non-Done issue with its fields, labels, relationships, and status.
For each, re-derive: should it still exist · is it one thing · are Type/Effort/Priority/Milestone still right · does AUTO/HITL still hold · is its Status honest.
Act:
- Stale, superseded, or unwanted → Done + Reject, reason in a comment.
- Outgrown its Effort, or several things → split into sub-issues, triaged as created.
- Shaped enough now → promote Backlog → Ready.
- In progress with no branch or PR → not claimed; return to Ready.
- HITL whose blocking step has resolved → re-label AUTO.
Comment only where something changed, saying what and why.
Report: counts by state, what changed, what you left, and what only a human can unblock.

Checks worth running every sweep

The Priority distribution test — more than roughly a fifth High means the field routes nothing.
Parentless Task issues. GitHub cannot enforce it; this sweep is the enforcement.
Open issues missing Effort, an autonomy label, or a milestone.
Ready issues whose criteria only their author could check.

Plus depuis ce dépôt

même dépôt

autonomous-issue-triage

exit-zero-labs/threat-forge

Select the next executable AUTO ThreatForge issue

2026-07-2712

issue-triage

exit-zero-labs/threat-forge

Shape one ThreatForge issue and populate Project 2 metadata without coding

2026-07-2712

fix-issue

exit-zero-labs/threat-forge

Compatibility alias for implementing a settled ThreatForge bug issue

2026-07-2712

implement-issue

exit-zero-labs/threat-forge

Orchestrate one settled ThreatForge issue through verification and preflight

2026-07-2712

issues-clarify

exit-zero-labs/threat-forge

Re-derive and repair the ThreatForge GitHub board after roadmap or code drift

2026-07-2712

issues-report

exit-zero-labs/threat-forge

Produce a read-only maintainer briefing from ThreatForge Project 2

2026-07-2712

name	issues-refresh
description	Sweep the whole board and re-triage it — re-derive every non-Done issue's fields, correct drift, split what has outgrown itself, close what no longer deserves to exist, and promote what is now shaped. A long, high-reasoning periodic pass. Use to audit a board that has grown untrustworthy, after a batch of merges, or when a milestone ships.

Refresh the board

Guardrails

Re-derive, never rubber-stamp. Decide each field as if seeing the issue fresh. A sweep that confirms everything it looks at has not audited anything.
Do not churn what is already right. Record an issue as verified and move on. Rewriting a correct description to look busy costs review attention and buries the changes that matter.

Procedure

Establish the ground truth first: current main, every open pull request, and which milestones have shipped. Drift is measured against reality, not against the last sweep.
Pull every non-Done issue with its fields, labels, relationships, and status.
For each, re-derive: should it still exist · is it one thing · are Type/Effort/Priority/Milestone still right · does AUTO/HITL still hold · is its Status honest.
Act:
- Stale, superseded, or unwanted → Done + Reject, reason in a comment.
- Outgrown its Effort, or several things → split into sub-issues, triaged as created.
- Shaped enough now → promote Backlog → Ready.
- In progress with no branch or PR → not claimed; return to Ready.
- HITL whose blocking step has resolved → re-label AUTO.
Comment only where something changed, saying what and why.
Report: counts by state, what changed, what you left, and what only a human can unblock.

Checks worth running every sweep

The Priority distribution test — more than roughly a fifth High means the field routes nothing.
Parentless Task issues. GitHub cannot enforce it; this sweep is the enforcement.
Open issues missing Effort, an autonomy label, or a milestone.
Ready issues whose criteria only their author could check.