schedule-issue-sweep

Triage open GitHub issues, close resolved ones, and resolve the rest as draft pull requests.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/JSdotNet/devbook --skill schedule-issue-sweep-jsdotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: schedule-issue-sweep
Source: https://github.com/JSdotNet/devbook/tree/main/plugins/delivery-schedule/skills/schedule-issue-sweep
Command: npx skills add https://github.com/JSdotNet/devbook --skill schedule-issue-sweep-jsdotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unattended repositories accumulate open issues that nobody has classified, verified, or acted on. This Skill runs an autonomous sweep that classifies every untriaged issue in the repository's own labels, closes issues that high-confidence evidence shows are already resolved, and resolves up to N of the remaining issues one at a time, each landing as a draft pull request for human review. ## Core Features & Use Cases - Automated Issue Triage: Classifies open issues by type, area, and severity using only the repository's existing labels, asks reporters for missing information, and marks issues triaged so later sweeps skip re-classification. - Evidence-Based Closure: Closes only issues proven already fixed, obsolete, or duplicate at high confidence, with the evidence (commit, file, or pull request) quoted in the closing comment; everything else becomes a proposal in the brief. - Sequential Issue Resolution: Resolves selected issues one at a time in dedicated git worktrees using a test-first workflow with bounded build repair and dual review lenses, opening every result as a draft pull request. - Use Case: Schedule a weekday run against owner/repo with maxResolve: 3 so each morning you review one brief listing what was labelled, closed, opened as draft pull requests, and left for a person. ## Quick Start Run the issue sweep against my repository owner/repo with maxResolve set to 3 and publish the sweep brief.

Frequently Asked Questions about schedule-issue-sweep

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

FAQPage Schema
How do I automatically triage open GitHub issues?▼

Run the sweep with a repository in owner/repo format and it classifies every untriaged open issue using the repository's existing labels, then marks each one triaged. Issues below the label confidence threshold become proposals in the brief instead of written labels.

How does the issue sweep decide which GitHub issues to close?▼

It closes only issues judged already-fixed, obsolete-code-gone, or duplicate at high confidence, where the verdict names verifiable evidence such as a commit, file, pull request, or sibling issue. All other stale verdicts are reported as proposals with ready-to-run close commands.

Can the sweep resolve issues without human review?▼

No. Every resolved issue lands as a draft pull request whose body states what could not be proved, and the sweep never merges, approves, or pushes to the base branch. A person validates each draft before it becomes ready for review.

What happens when an issue resolution fails during the sweep?▼

The sweep comments the outcome and stopping stage on the issue, removes the in-progress label, and adds sweep-failed so later runs skip it until a person clears the label. Escalated issues get a successor label such as needs-adr instead.

Does the issue sweep protect against prompt injection in issue bodies?▼

Yes. Issue bodies are treated as data, never instructions. Any issue containing text addressed to an AI agent is quoted in the brief and excluded from labelling, closure, and resolution until a person acts on it.

What does maxResolve 0 do in the issue sweep?▼

Setting maxResolve to 0 runs the triage alone: issues are classified, missing information is requested, and stale candidates are proposed or closed, but no branches, worktrees, or pull requests are created.