How do I install the Triage skill?

Run npx skillmds@latest add freema/triage in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Triage safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Triage?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Triage free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Triage?

freema (@freema) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Triage by freema — Agent Skill

Name: Triage
Author: freema

Triage

Runs new and updated pull requests through the triage checklist (size, description, failing checks) and proposes labels and at most one comment per pull request. Use on the triage routine or when asked to triage pull requests.

freema 51dfe19 3.3 KB Updated Sep 17, 2026

File contents

Pull request triage

Phase 1: find the work

Read memory/progress.md: the repositories to watch and the pull requests already triaged, with the head commit each was triaged at.
For each repository, list_pull_requests with state: open, sorted by updated. A pull request is work when it is not in the progress file or its head commit changed since it was triaged. Skip drafts and pull requests opened by bots.

Phase 2: the checklist

pull_request_read with method: get, get_files and get_status for each pull request that is work, then:

Check	Rule	Label	Comment
Size	more than 400 changed lines or more than 20 files	`size/large`	none
Size	400 changed lines or fewer	`size/small`	none
Description	body empty or under 30 characters, or no line saying what and why	`needs-description`	one comment asking for what changed, why, and how it was verified
Checks	at least one check failing or errored	`ci-failing`	one comment naming the failing check
Checks	checks still pending	none	none; look again next run

A pull request gets every label that applies and at most one comment; when both the description and the checks fail, one comment covers both.

Phase 3: apply, with approval

For each pull request, propose the labels through issue_write (labels only, never state, title or body) and the comment through add_issue_comment. Each call asks; say in one line what you are about to send before you call.
A label the repository does not have: never create it silently. label_write asks; if the person denies, mention the missing label in the run report instead.
Append the run report to memory/runs/<YYYY-MM-DD>.md and rewrite memory/progress.md with the head commit of every pull request triaged.

Stop conditions

No repositories in memory/progress.md: report it and stop; the person fills the list in.
A pull request already carries a triage comment from you: labels only, never a second comment for the same finding.
More than 30 pull requests to triage in one run: the 30 most recently updated, and say how many wait.
The person denies something on a pull request: skip the rest of that pull request, continue with the next one.

Output format

# Triage <YYYY-MM-DD> <HH:MM>

- <owner/repo>#<n> <title>: <labels> — comment: <yes/no> — <findings>

Nothing to say: #<n>, #<n>
Waiting: <count> more

---name: triagedescription: Runs new and updated pull requests through the triage checklist (size, description, failing checks) and proposes labels and at most one comment per pull request. Use on the triage routine or when asked to triage pull requests.---# Pull request triage## Phase 1: find the work1. Read `memory/progress.md`: the repositories to watch and the pull requests already triaged, with the head commit each was triaged at.2. For each repository, `list_pull_requests` with `state: open`, sorted by `updated`. A pull request is work when it is not in the progress file or its head commit changed since it was triaged. Skip drafts and pull requests opened by bots.## Phase 2: the checklist3. `pull_request_read` with `method: get`, `get_files` and `get_status` for each pull request that is work, then:| Check | Rule | Label | Comment || ----------- | ----------------------------------------------------------------- | ------------------- | ----------------------------------------------------------------- || Size | more than 400 changed lines or more than 20 files | `size/large` | none || Size | 400 changed lines or fewer | `size/small` | none || Description | body empty or under 30 characters, or no line saying what and why | `needs-description` | one comment asking for what changed, why, and how it was verified || Checks | at least one check failing or errored | `ci-failing` | one comment naming the failing check || Checks | checks still pending | none | none; look again next run |4. A pull request gets every label that applies and at most one comment; when both the description and the checks fail, one comment covers both.## Phase 3: apply, with approval5. For each pull request, propose the labels through `issue_write` (labels only, never state, title or body) and the comment through `add_issue_comment`. Each call asks; say in one line what you are about to send before you call.6. A label the repository does not have: never create it silently. `label_write` asks; if the person denies, mention the missing label in the run report instead.7. Append the run report to `memory/runs/<YYYY-MM-DD>.md` and rewrite `memory/progress.md` with the head commit of every pull request triaged.## Stop conditions- No repositories in `memory/progress.md`: report it and stop; the person fills the list in.- A pull request already carries a triage comment from you: labels only, never a second comment for the same finding.- More than 30 pull requests to triage in one run: the 30 most recently updated, and say how many wait.- The person denies something on a pull request: skip the rest of that pull request, continue with the next one.## Output format```markdown# Triage <YYYY-MM-DD> <HH:MM>- <owner/repo>#<n> <title>: <labels> — comment: <yes/no> — <findings>Nothing to say: #<n>, #<n>Waiting: <count> more```

Frequently asked questions