repo-issue-triage

Cross-reference GitHub issues against PRs and main branch for triage reports.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/spboyer/repo-issue-triage --skill repo-issue-triage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-issue-triage
Source: https://github.com/spboyer/repo-issue-triage/tree/main
Command: npx skills add https://github.com/spboyer/repo-issue-triage --skill repo-issue-triage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the tedious and time-consuming process of triaging GitHub issues and pull requests, helping maintain a clean and organized repository.

Core Features & Use Cases

  • Automated Triage: Cross-references issues with PRs and codebase to recommend closure or action.
  • PR Health Monitoring: Checks CI status, reviews, and threads for open PRs.
  • Use Case: Regularly audit your repository's issues to identify stale items, those already fixed by merged PRs, or those covered by ongoing work, ensuring your backlog is always actionable.

Quick Start

Use the repo-issue-triage skill to audit all open issues and PRs in the current repository.

Frequently Asked Questions about repo-issue-triage

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

FAQPage Schema
How do I automate GitHub issue triage for my repository?

Automate GitHub issue triage by cross-referencing open issues against pending pull requests, merged pull requests, and the main branch to generate actionable close or keep recommendations. This skill uses the gh CLI to audit your repository backlog and output structured markdown reports.

Can I monitor pull request health and CI status automatically?

Yes, you can monitor pull request health automatically by checking CI status, code reviews, and comment threads for open pull requests. The skill evaluates PR health alongside issue triage to ensure your repository backlog remains actionable and clean.

What's the best way to identify stale GitHub issues already fixed by merged PRs?

The best way to identify stale GitHub issues fixed by merged pull requests is cross-referencing open issues against the merged PR history and current main branch codebase. This automated process flags resolved issues for recommended closure.

Do I need the GitHub CLI to audit repository issues and PRs?

Yes, you need the GitHub CLI (gh) installed to audit repository issues and pull requests. The skill also uses grep and glob CLI tools alongside a session SQL database for tracking triage data and generating structured markdown reports.

How does issue triage cross-reference open issues with ongoing work?

Issue triage cross-references open issues with ongoing work by scanning pending pull requests, merged PRs, and the current main branch codebase. It identifies issues covered by active development and produces actionable close or keep recommendations.

What format does the automated issue triage report use?

The automated issue triage report uses structured markdown format to deliver actionable close and keep recommendations. It cross-references open issues and pull requests against the codebase and stores tracking data in a session SQL database.