issue-triage

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.

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.

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.

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.

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.

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.