github-issue-update

Audits open GitHub issues and applies approved close, comment, and label changes in bulk.

1|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/mjun0812/skills --skill github-issue-update-mjun0812
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-issue-update
Source: https://github.com/mjun0812/skills/tree/main/skills/github/github-issue-update
Command: npx skills add https://github.com/mjun0812/skills --skill github-issue-update-mjun0812

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Open issues accumulate over time and become stale, duplicated, or mislabeled, making the issue tracker hard to navigate. Manually reviewing every open issue to decide what to close, update, or relabel is tedious and error-prone. ## Core Features & Use Cases - Automated Triage Detection: Scans all open issues via the GitHub CLI and identifies close candidates (duplicates, resolved, stale over 90 days), comment additions, and label mismatches against the repository's existing labels. - Approval-Gated Bulk Apply: Presents a prioritized summary and uses multi-step user confirmation before writing anything, then applies changes in parallel batches while respecting GitHub rate limits. - Use Case: Ask the agent to tidy up your repository's issue tracker; it reviews all open issues, proposes closing 3 duplicates and 2 stale items, fixing labels on 4 others, and applies everything only after you approve. ## Quick Start Ask the agent to review and organize the open issues in this repository, then approve the proposed close, comment, and label changes.

Frequently Asked Questions about github-issue-update

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

FAQPage Schema
How do I bulk close stale GitHub issues automatically?

This skill lists all open issues with gh issue list, flags issues whose updatedAt is older than 90 days with no comments or vague completion criteria as stale, and closes them with an explanatory comment after you approve the summary.

How to detect duplicate GitHub issues in a repository?

It compares open issues by normalized title match, three or more shared keywords, or overlapping body tokens. When duplicates are found, the older issue is kept and the newer one is proposed for closure with a reference comment.

Does it create new labels on GitHub automatically?

No. Label changes are restricted to labels that already exist in the repository, fetched via gh label list. It only adds or removes existing labels and never invents new ones.

Can it modify issues without my confirmation?

No. All write operations, including closes, comments, and label changes, are gated behind an approval step using AskUserQuestion. You can approve all, select individually, inspect details, or cancel everything.

What happens if too many issues need updating at once?

Candidates are prioritized (resolved closes first, then duplicates, stale, labels, comments) and truncated by the --max limit, which defaults to 100. Parallel execution is batched in groups of 5-10 to respect GitHub secondary rate limits.