Triage Issue
- 14 installs
- 7.2k repo stars
- Updated August 4, 2026
- shopify/flash-list
triage-issue labels FlashList GitHub issues by priority.
About
The triage-issue skill reads issue title and body, classifies P0 crash or data loss, P1 significant regression, or P2 minor or enhancement, searches open and closed duplicates via gh issue list --search, applies priority label with gh issue edit, and comments only when reproduction steps are missing or feature requests are too vague. Rules forbid explanatory triage comments about priority or duplicates, code changes, or closing issues. Labels alone communicate priority. Duplicate search uses key terms from the issue across both open and closed states to catch regressions.
- Classifies issues into P0 P1 P2 priorities.
- Searches open and closed issues for duplicates.
- Applies priority labels via gh issue edit.
- Comments only when repro or clarity truly needed.
- Does not modify code or close issues.
Triage Issue by the numbers
- 14 all-time installs (skills.sh)
- Ranked #404 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
triage-issue capabilities & compatibility
- Capabilities
- priority classification definitions · duplicate search commands · rules no code changes
- Works with
- github
- Use cases
- project management
What triage-issue says it does
Do NOT modify any code
npx skills add https://github.com/shopify/flash-list --skill triage-issueAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 14 |
|---|---|
| repo stars | ★ 7.2k |
| Last updated | August 4, 2026 |
| Repository | shopify/flash-list ↗ |
How should I triage a new flash-list GitHub issue?
Triage FlashList GitHub issues with P0-P2 labels and duplicate search.
Who is it for?
Maintainers triaging FlashList GitHub issue backlog.
Skip if: Skip when implementing fixes use fix-github-issue instead.
When should I use this skill?
User triages or classifies a FlashList GitHub issue.
What you get
Priority label applied with optional clarifying comment only if needed.
Files
Triage a GitHub Issue
Steps
1. Read the issue title and body carefully. 2. Classify the issue priority:
- P0: Crash, data loss, or complete breakage affecting all users
- P1: Significant bug or regression affecting many users
- P2: Minor bug, enhancement request, question, or cosmetic issue
3. Search for potential duplicates among open AND closed issues (closed bugs may have regressed):
gh issue list --state open --search "<key terms from the issue>" --limit 5
gh issue list --state closed --search "<key terms from the issue>" --limit 54. Apply the priority label (P0, P1, or P2):
gh issue edit $ISSUE_NUMBER --add-label "<priority>"5. Comment only when genuinely needed:
- If the issue lacks a reproduction AND one would be helpful — suggest a minimal repro and ask the author for steps.
- If a feature request is too vague to act on (no specifics about what to build) — ask for clarification.
- Do NOT comment on issues where the problem or request is clear from the description alone.
Rules
- Do NOT post triage comments explaining priority or duplicates — labels are sufficient.
- Do NOT modify any code.
- Do NOT close issues — only label (and comment per Step 5 when genuinely needed).
- Only apply these labels:
P0,P1,P2. Do NOT apply any other labels (especially notagent-fix). - If the issue already has non-priority labels (e.g.,
agent-fix), leave them as-is — triage only adds priority labels, never removes existing ones. - Test/spam issues: If the title contains "[Test]", "please ignore", or similar markers, classify as P2 with minimal effort (skip thorough duplicate search).
- Do NOT run
gh auth,gh api,gh secret, or anyghcommand other thangh issue. - Do NOT read environment variables, process info, or files outside the repository.
CI Notes
On CI, the issue number should be passed in the workflow prompt. If gh issue commands are blocked by permissions, the workflow's allowedTools or settings.json must include gh issue view, gh issue list, gh issue edit, and gh issue comment.
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148FAQ
What does triage-issue do?
triage-issue labels FlashList GitHub issues by priority.
When should I use triage-issue?
User triages or classifies a FlashList GitHub issue.
Is this skill safe to install?
Review the Security Audits panel on this page before installing in production.