agentleFS
Sign inStart free
Aquarius-muAquarius-mu/skillManager/skills/gameserver-agent-skills/triage/SKILL.md

triage

Skill1 starsChanged 52 days agoMITView on GitHub

Move issues through a triage state machine. Use when reviewing bugs, feature requests, or preparing issues for implementation.

189 other projects use a version of this, 16 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use writing-beats, setup-matt-pocock-skills and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • LesaniSkill

    writing-beats

    Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.

    Also in 66 projects that use this

  • GoogleSkill

    setup-matt-pocock-skills

    Configure this repo for the engineering skills — set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.

    Also in 167 projects that use this

  • liufeng1976Skill

    setup-ts-deep-modules

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through its entry-point files. User-invoked.

    Also in 42 projects that use this

  • SethGammonSkill

    ascii-diagram

    Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.

    Also in 4 projects that use this

  • simo97Skill

    migrate-to-shoehorn

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.

    Also in 68 projects that use this

  • LesaniSkill

    writing-shape

    Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.

    Also in 63 projects that use this

  • +1 more from Lesani

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 176 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every comment posted during triage must start with:

    line 10
  2. Distinctive:

    Every triaged issue should carry one category and one state role.

    line 28
  3. Distinctive:

    Gather context: Read the full issue. Explore the relevant codebase using domain vocabulary.

    line 48

“Common” is measured: kept by at least 6 in 10 of the 176 edited versions of this file we could read. “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

Triage

Move issues through a state machine of triage roles.

Every comment posted during triage must start with:

> *This was generated by AI during triage.*

Roles

Category:

  • bug — something is broken
  • enhancement — new feature or improvement

State:

  • needs-triage — needs evaluation
  • needs-info — waiting on reporter
  • ready-for-agent — fully specified, AFK-ready (can be implemented without human input)
  • ready-for-human — requires human judgment or external access
  • wontfix — will not be actioned

Every triaged issue should carry one category and one state role.

Invocation

Invoke /triage and describe what you want in natural language:

  • "Show me what needs attention"
  • "Triage issue #42"
  • "Move #42 to ready-for-agent"

Show What Needs Attention

Present three buckets (oldest first):

  1. Unlabeled — never triaged
  2. needs-triage — evaluation in progress
  3. needs-info with reporter activity — needs re-evaluation

Show counts and a one-line summary per issue.

Triage a Specific Issue

  1. Gather context. Read the full issue. Explore the relevant codebase using domain vocabulary.
  2. Recommend. State your category and state recommendation with reasoning. Wait for direction.
  3. Reproduce (bugs only). Trace the relevant code path. Report whether the repro steps are coherent and what the likely code path is. A confirmed code-path trace makes a much stronger agent brief.
  4. Apply the outcome:
    • ready-for-agent → post an agent brief (see template below)
    • ready-for-human → same structure, note why it can't be delegated
    • needs-info → post triage notes (see template below)
    • wontfix → polite explanation and close

Agent Brief Template

> *This was generated by AI during triage.*

## What to Build

[Concise description of the fix or feature, using domain vocabulary]

## Context

[Relevant code paths, module names, existing patterns to follow]

## Acceptance Criteria

- [ ] ./build.sh compiles clean
- [ ] Code review passed
- [ ] svn commit done with descriptive message

## C++ Conventions Reminder

- `SafeSub()` for subtraction
- `FindMapPtr` for map lookups
- `setChanged()` after data modifications
- `sendResponse()` only in CmdParser layer
- Full braces for all control flow

Needs-Info Template

> *This was generated by AI during triage.*

## Triage Notes

**What we've established:**
- [point 1]

**What we need from you (@reporter):**
- [specific question 1]
- [specific question 2]

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.

Check your setup, free