agentleFS
ric03uecric03uec/clawrium/.claude/skills/itx-triage/SKILL.md

itx-triage

Skill67 starsChanged 2 months agoApache-2.0View on GitHub

Review issues without workflow labels and assign appropriate labels

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
  1. Very specific:

    Needs more info: Add needs-triage label

    line 29
  2. Very specific:

    Ready to plan: Add planning label

    line 30
  3. Very specific:

    Bug report: Ensure bug label is present, add needs-triage

    line 31
  4. Very specific:

    Clear and actionable: Add planning label

    line 32
  5. Distinctive:

    Don't re-triage issues that already have workflow labels

    line 77

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Issue Triage

Find and triage issues that don't have workflow labels.

Instructions

  1. Find Unlabeled Issues: List issues without workflow labels
    gh issue list --state open --json number,title,labels,createdAt --limit 50
  2. Filter: Identify issues that do NOT have any of these labels:
    • needs-triage
    • planning
    • ready
    • in-progress
    • in-review
  3. For Each Unlabeled Issue:
    • Fetch full details: gh issue view <number>
    • Analyze the title and description
    • Determine appropriate action:
      • Needs more info: Add needs-triage label
      • Ready to plan: Add planning label
      • Bug report: Ensure bug label is present, add needs-triage
      • Clear and actionable: Add planning label
  4. Apply Labels:
    gh issue edit <number> --add-label "<label>"
  5. 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> ```
  6. Return: Summary of triaged issues

Workflow Labels

LabelMeaning
needs-triageNeeds more information or clarification
planningReady for implementation planning
readyPlan complete, ready for execution
in-progressCurrently being worked on
in-reviewPR 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.