sweep-issues

Score open GitHub issues against a 10-item quality checklist and suggest labels.

2|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/rnwolfe/forge --skill sweep-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sweep-issues
Source: https://github.com/rnwolfe/forge/tree/main/.claude/skills/sweep-issues
Command: npx skills add https://github.com/rnwolfe/forge --skill sweep-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sweep open repository issues to surface tickets that lack sufficient detail or structure for execution, so teams can prioritize refinement and reduce wasted implementation effort.

Core Features & Use Cases

  • Quality scoring: Evaluates issues against a 10-item checklist (summary, scope, architecture, acceptance criteria, tests, docs, labels, etc.) and assigns Present/Weak/Missing ratings.
  • Selective filtering: Optionally restricts the sweep by labels or phases to focus on specific backlogs.
  • Actionable output: Presents a compact summary table with scores and verdicts and, with explicit approval, applies backlog/needs-refinement or suggests backlog/ready labels and optional gap comments.
  • Use case: A product manager runs the sweep to quickly identify partially-specified feature requests and generate a prioritized list for refinement sprints.

Quick Start

Run /sweep-issues to audit open issues and produce a scored summary with suggested labels and required approval before any changes.

Frequently Asked Questions about sweep-issues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit open GitHub issues for quality and readiness?

Auditing open GitHub issues involves evaluating them against a structured 10-item quality checklist to score completeness and identify gaps. This process assigns Present, Weak, or Missing ratings for criteria like scope, architecture, and acceptance criteria.

How do I automatically label and triage a GitHub backlog?

Automatically labeling and triaging a GitHub backlog requires scoring open issues against a quality checklist and generating suggested labels. This Skill prepares backlog, needs-refinement, or ready labels and gap comments, applying them only after explicit user approval.

What is the best way to identify low-quality feature requests in a repository?

Identifying low-quality feature requests means sweeping open issues to surface tickets lacking sufficient detail or structure for execution. This Skill selectively filters by labels or phases to score bugs, enhancements, and feature requests for prioritization.

Can I filter the issue sweep to only audit specific backlog phases?

Yes, you can filter the issue sweep to focus on specific backlogs. The Skill optionally restricts the audit by labels or phases, allowing you to target and score specific subsets of bugs, enhancements, and feature requests within your repository.

Does the automated issue triage apply labels without user confirmation?

No, the automated issue triage does not apply labels automatically. It generates a compact summary table with scores, suggested labels, and optional gap comments, requiring explicit user approval before making any changes to the repository issues.