-
Notifications
You must be signed in to change notification settings - Fork 0
COOL IDEA: issue completion scanner #603
Copy link
Copy link
Open
Labels
area:toolingPrimary work area: tooling.Primary work area: tooling.feature:tooling-releaseMethod feature tooling-release.Method feature tooling-release.lane:cool-ideasMethod source lane cool-ideas.Method source lane cool-ideas.legend:ideaMethod legend idea.Method legend idea.priority:laterDeferred or speculative work.Deferred or speculative work.status:availableOpen and available for prioritization; not blocked or actively in progress.Open and available for prioritization; not blocked or actively in progress.type:enhancementMethod issue type enhancement.Method issue type enhancement.
Description
Metadata
Metadata
Assignees
Labels
area:toolingPrimary work area: tooling.Primary work area: tooling.feature:tooling-releaseMethod feature tooling-release.Method feature tooling-release.lane:cool-ideasMethod source lane cool-ideas.Method source lane cool-ideas.legend:ideaMethod legend idea.Method legend idea.priority:laterDeferred or speculative work.Deferred or speculative work.status:availableOpen and available for prioritization; not blocked or actively in progress.Open and available for prioritization; not blocked or actively in progress.type:enhancementMethod issue type enhancement.Method issue type enhancement.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Cool idea
Add an issue completion scanner that finds open issues whose stated failure mode is already resolved on
origin/main.The scanner would not auto-close issues. It would produce a reviewed candidate list with evidence, for example:
origin/mainWhy it helps
The repo has hundreds of open issues, and several migrated backlog cards are already partially or fully resolved by later work. A scanner would turn cleanup into an evidence-led review queue instead of a manual title-by-title audit.
Suggested shape
node scripts/issue-completion-scan.ts --label lane:bad-code --base origin/main --jsonThe output should include exact files/commands used as evidence and avoid changing GitHub state.
Origin
Idea came up after noticing issue #278 appeared resolved on current
mainwhile selecting the second bad-code batch.