triaging-issues

Manage GitHub issue statuses by verifying against code, merged PRs, and ADRs.

1|Updated Mar 20, 2025
One-click install
npx skills add https://github.com/asanexample/platform --skill triaging-issues-asanexample
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triaging-issues
Source: https://github.com/asanexample/platform/tree/main/.claude/skills/triaging-issues
Command: npx skills add https://github.com/asanexample/platform --skill triaging-issues-asanexample

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps maintain an accurate and up-to-date GitHub issue board by providing a structured process for triaging issues.

Core Features & Use Cases

  • Issue Verification: Decide the true state of each issue by verifying against primary sources like code, merged PRs, and ADRs.
  • Board Reconciliation: Ensure the issue board reflects the actual state of the codebase.
  • Automated Triage: Use scripts and tools to streamline the process of closing, labeling, and updating issues.

Quick Start

Use the triaging-issues skill to update the status of all open issues in your repository.

Frequently Asked Questions about triaging-issues

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

FAQPage Schema
How do I keep my GitHub issue board updated with the actual codebase state?

To keep your GitHub issue board updated, you can use automated triaging scripts to verify issues against primary sources like merged PRs and ADRs, ensuring the board reflects the actual codebase state.

What is the best way to automate GitHub issue triage for project management?

The best way to automate GitHub issue triage is by running scripts that apply a structured process to verify, label, and update issue statuses, streamlining the reconciliation of your project management workflows.

Do I need GitHub API access to automate issue management and closing?

Yes, you need GitHub API access and knowledge of common GitHub commands to automate issue management, as the triaging process requires scripts to query repositories and update issue statuses.

Why does my GitHub issue board show outdated statuses after merging code?

Your GitHub issue board shows outdated statuses because issues are not automatically reconciled with merged code, requiring a triage process to verify true states against primary sources and close resolved items.

Can I use scripts to verify GitHub issues against merged pull requests?

Yes, you can use scripts to verify GitHub issues against merged pull requests, applying a structured triage process to decide the true state of each issue and update the board accordingly.