issue-triage

Classify and rank open GitHub issues into actionable JSON manifests.

30|12|Updated Jun 21, 2026

Search Tags:#automation #productivity #github #backlog #triage #gardening

Ready to run

npx skills add https://github.com/anthony-chaudhary/fak --skill issue-triage-anthony-chaudhary

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: issue-triage
Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/issue-triage
Command: npx skills add https://github.com/anthony-chaudhary/fak --skill issue-triage-anthony-chaudhary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This skill solves the problem of a rotting GitHub issue backlog where labels are missing, priorities are undefined, and stale issues accumulate, preventing teams from focusing on high-impact work.

Core Features & Use Cases

Deterministic Ranking: Uses a transparent scoring formula to rank issues by priority, helping teams identify what to work on next.
Mechanical Gardening: Automates the identification and batch-processing of stale issues and dormant questions.
Read-Only Safety: Operates with a strict read-only fetch-and-propose workflow, ensuring that no changes are applied to GitHub without explicit operator approval.

Quick Start

Ask the assistant to triage the open issue backlog and propose gardening actions for the last thirty days.

Frequently Asked Questions about issue-triage

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

FAQPage Schema

How do I automate triage for a stale GitHub issue backlog?▼

Automating GitHub backlog triage involves classifying open issues, ranking them by priority, and proposing maintenance actions for stale items. This skill uses a deterministic scoring formula to identify orphans and priority gaps while maintaining a read-only safety boundary.

What is backlog gardening for GitHub repositories?▼

Backlog gardening is the process of identifying and batch-processing stale GitHub issues, dormant questions, and items with missing labels. It operates on repository issue data to propose maintenance actions that improve project organization and highlight high-impact work.

Do I need the GitHub CLI to rank and classify open issues?▼

Yes, you need the GitHub CLI installed to fetch repository issue data. The skill requires the CLI and a project-specific triage helper script to generate actionable JSON manifests for operator review.

Can I automatically close or label stale GitHub issues without manual review?▼

No, you cannot automatically apply changes without manual review. The skill operates with a strict read-only fetch-and-propose workflow, ensuring that no modifications are applied to GitHub without explicit operator approval.

How do I identify orphaned and low-priority issues in my GitHub project?▼

You can identify orphaned and low-priority issues by analyzing repository issue data with a transparent scoring formula. The skill evaluates open issues to find priority gaps, undefined priorities, and stale items that prevent teams from focusing on high-impact work.

What's the best way to propose maintenance actions for GitHub repository issues?▼

The best way to propose maintenance actions is to run a triage helper script that generates a JSON manifest of ranked issues. This manifest identifies orphans, stale items, and priority gaps for operator review without applying changes directly.