itx-triage
Skill67 starsChanged 2 months agoApache-2.0View on GitHub
Review issues without workflow labels and assign appropriate labels
In this repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- clawctl-lmworkSkill
- clawctlSkill
- clawctl-uatSkill
- create-playwrightSkill
- create-vhsSkill
- itx-bug-newSkill
- itx-bug-updateSkill
- itx-executeSkill
- itx-issue-newSkill
- itx-issue-updateSkill
- itx-noteSkill
- itx-plan-createSkill
- itx-plan-scaffoldSkill
- itx-pr-statusSkill
- itx-releaseSkill
- itx-review-prSkill
- itx-verifySkill
- sync-upstreamSkill
- tddSkill
- blog-authorSkill
- daily-digestSkill
- docs-syncSkill
- issue-triageSkill
- release-watcherSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Needs more info: Add needs-triage label
- Very specific: line 30
Ready to plan: Add planning label
- Very specific: line 31
Bug report: Ensure bug label is present, add needs-triage
- Very specific: line 32
Clear and actionable: Add planning label
- Distinctive: line 77
Don't re-triage issues that already have workflow labels
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Issue Triage
Find and triage issues that don't have workflow labels.
Instructions
- Find Unlabeled Issues: List issues without workflow labels
gh issue list --state open --json number,title,labels,createdAt --limit 50 - Filter: Identify issues that do NOT have any of these labels:
needs-triageplanningreadyin-progressin-review
- For Each Unlabeled Issue:
- Fetch full details:
gh issue view <number> - Analyze the title and description
- Determine appropriate action:
- Needs more info: Add
needs-triagelabel - Ready to plan: Add
planninglabel - Bug report: Ensure
buglabel is present, addneeds-triage - Clear and actionable: Add
planninglabel
- Needs more info: Add
- Fetch full details:
- Apply Labels:
gh issue edit <number> --add-label "<label>" Add Triage Comment:
**Triage Decision**: <label applied> <brief rationale> --- <details> <summary>Prompt Log</summary> **Stage**: triage **Skill**: /itx-triage **Timestamp**: <ISO timestamp> **Model**: <model> ```prompt <user prompt that triggered triage></details> ```- Return: Summary of triaged issues
Workflow Labels
| Label | Meaning |
needs-triage | Needs more information or clarification |
planning | Ready for implementation planning |
ready | Plan complete, ready for execution |
in-progress | Currently being worked on |
in-review | PR open for review |
Notes
- Focus on issues that fell through the cracks
- Don't re-triage issues that already have workflow labels
- Be conservative - when in doubt, use
needs-triage
Prompt Logging
REQUIRED: For each triaged issue, append prompt log to .itx/<N>/00_PLAN.md.
See AGENTS.md for format specification.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

