github-triage

Triage issues in the current repo using a label-based state machine. Infer the repo from git remote . Use gh for all GitHub operations. Every comment or issue posted to GitHub during triage must include the following disclaimer at the top of the comment body, before any other content: Every issue should have exactly one state label and one category label. If an issue has conflicting state labels (e.g. both needs-triage and ready-for-agent ), flag the conflict and ask the maintainer which state is correct before doing anything else. Provide a recommendation. An issue can only move along these transitions. The maintainer can override any state directly (see Quick State Override below), but the skill should flag if the transition is unusual.