What problem does it solve? Returning to a repository after time away means facing a pile of new, changed, and commented issues with no clear sense of what matters. This Skill performs a fast interactive triage sweep so you know what exists, what moved, and what burns — without reading every issue in full. ## Core Features & Use Cases - Incremental Sweep: Uses the GitHub CLI (gh) to list issues updated since the last check, classifying each as new or changed, with a rolling state document (<repo>/.reviews/triage/issues.md) so every run picks up where the previous one left off. - Issue-by-Issue Cycle: Presents each issue in under 10 lines — what it says, what changed, and a proposed urgency (alta/media/bassa) — then offers a closed action menu: tag on GitHub with real repo labels, mark for deep dive, add a note, skip, or stop. - Strict Boundaries: Proposes urgency but never decides it; applies only labels the user picks from the repo's actual label list; never assigns, closes, or comments on issues. - Use Case: After two weeks away from a project, ask for a triage run to get a sorted queue of the 12 issues that changed, tag three as bugs, and mark two for a deep-dive review later. ## Quick Start Triage the open issues in this repository that changed since my last check and walk me through them one by one.
