Триаж задач и PR
Ведёт задачи через машину состояний: needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix; категории bug и enhancement. Воспроизводит баги, задаёт уточняющие вопросы, пишет устойчивые брифы для агентов и ведёт базу отклонённых идей. Каждый комментарий помечается как сгенерированный AI. Вызывается только вручную.
Ставится на компьютере
С телефона скилл не поставить: Claude Code работает на Windows, macOS и Linux. Отправьте ссылку себе и откройте её на компьютере.
Способ установки
Откройте Терминал и вставьте команду:
curl -fsSL https:/ / claudeskills.ru/ install/ triage | bashСкилл ляжет в папку ~/.claude/skills/triage/. Если Claude Code уже открыт, а папки skills раньше не было, наберите в нём /reload-skills. Посмотреть скрипт
Карточка
triage- mattpocock
- на английском, задачу ставите по-русски
- SKILL.md
- AGENT-BRIEF.md
- agents/ · 1 файл
- OUT-OF-SCOPE.md
Похожие скиллы
- РазработкаНастройка скиллов Мэтта Покока
Разовая настройка репозитория для инженерных скиллов: трекер задач, метки триажа, глоссарий и ADR.
setup-matt-pocock-skills· mattpocock - РазработкаРеализация задачи
Claude реализует задачу по тикету или спеке: через TDD, с проверкой типов и финальным ревью.
implement· mattpocock - РазработкаСпека из обсуждения
Claude превращает текущее обсуждение в спеку и публикует её в трекер задач — без дополнительных вопросов.
to-spec· mattpocock - РазработкаGrill Me: допрос плана
Самый известный скилл Мэтта Покока: Claude жёстко допрашивает вас по плану, пока он не станет ясным.
grill-me· mattpocock - РазработкаАудит архитектуры кодовой базы
Claude ищет в коде мелкие модули, которые стоит углубить, и выдаёт наглядный HTML-отчёт с диаграммами.
improve-codebase-architecture· mattpocock - РазработкаДопрос плана с документацией
Жёсткое интервью по плану или дизайну, по ходу которого Claude пишет глоссарий и ADR.
grill-with-docs· mattpocock
Статьи по теме
- Что такое Claude Skills и зачем они нужныClaude Skills — модульные навыки для ИИ-ассистента Claude. Узнайте, что это, как установить, создать свой skill и использовать в Claude Code. Примеры и инструкции.
- Настройка скиллов Claude: как устроен SKILL.md и где хранить скиллыНастройка скиллов Claude: из чего состоит SKILL.md, куда класть папку, как написать description и проверить, что скилл срабатывает. CLAUDE.md — отдельно.
- Claude Code в России: как пользоваться и работает ли в 2026Работает ли Claude Code в России: страны нет в списке Anthropic, оплата доступ не открывает. Как использовать Claude Code из поддерживаемой страны и где оплата.
Текст инструкции · SKILL.md
Оригинал инструкции (англ.)
Это оригинал автора на английском. Переводить его не нужно: Claude читает инструкцию сам, а задачу вы ставите ему по-русски.
Move issues on the project issue tracker through a small state machine of triage roles.
If this repo treats external pull requests as a request surface (see the issue-tracker config), triage covers them too: a PR is an issue with attached code, using the same roles, same states, and same machine, with a few deltas marked "for a PR" below. Resolve a bare #42 to an issue or PR per the tracker config.
Every comment or issue posted to the issue tracker during triage must start with this disclaimer:
> *This was generated by AI during triage.*
Reference docs
- AGENT-BRIEF.md: how to write durable agent briefs
- OUT-OF-SCOPE.md: how the
.out-of-scope/knowledge base works
Roles
Two category roles:
bug: something is brokenenhancement: new feature or improvement
Five state roles:
needs-triage: maintainer needs to evaluateneeds-info: waiting on reporter for more informationready-for-agent: fully specified, ready for an AFK agentready-for-human: needs human implementationwontfix: will not be actioned
For a PR, the same states read against the attached code: ready-for-agent means a brief is attached and an agent should take the next step on the diff; ready-for-human means it's ready for a human to merge.
Every triaged issue should carry exactly one category role and one state role. If state roles conflict, flag it and ask the maintainer before doing anything else.
These are canonical role names. The actual label strings used in the issue tracker may differ. The mapping should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.
State transitions: an unlabeled issue normally goes to needs-triage first; from there it moves to needs-info, ready-for-agent, ready-for-human, or wontfix. needs-info returns to needs-triage once the reporter replies. The maintainer can override at any time; flag transitions that look unusual and ask before proceeding.
Invocation
The maintainer invokes /triage and describes what they want in natural language. Interpret the request and act. Examples:
- "Show me anything that needs my attention"
- "Let's look at #42" (issue or PR)
- "Move #42 to ready-for-agent"
- "What's ready for agents to pick up?"
Show what needs attention
Query the issue tracker and present three buckets, oldest first:
- Unlabeled: never triaged.
needs-triage: evaluation in progress.needs-infowith reporter activity since the last triage notes: needs re-evaluation.
When PRs are in scope, include external PRs in these buckets and tag each line [PR] or [issue]. Discovery surfaces only external PRs (the tracker config defines who counts as external), so a collaborator's in-flight PR is not triage work. This filter is discovery-only; an explicitly named PR is always triaged regardless of author.
Show counts and a one-line summary per item. Let the maintainer pick.
Triage a specific issue or PR
-
Gather context. Read the full issue or PR (body, comments, labels, author, dates; for a PR, the diff too). Parse any prior triage notes so you don't re-ask resolved questions. Explore the codebase using the project's domain glossary, respecting ADRs in the area. Run two checks against the codebase: (a) redundancy: search for an existing implementation of the requested behavior by domain concept (not just the request's wording), and report where you looked. If found, it's an already-implemented
wontfix(step 5). (b) prior rejection: read.out-of-scope/*.mdand surface any that resembles this request. -
Recommend. Tell the maintainer your category and state recommendation with reasoning, plus a brief codebase summary relevant to the request (including whether it's already implemented). Wait for direction.
-
Verify the claim. Before any grilling, check that the claim holds up. For a bug, reproduce it from the reporter's steps. For a PR, confirm the diff does what it claims: check it out, run the relevant tests or commands. Report what happened: confirmed (with code path), failed, or insufficient detail (a strong
needs-infosignal). A confirmed verification makes a much stronger agent brief. -
Grill (if needed). If the request needs fleshing out, call the Skill tool twice, for "grilling" and "domain-modeling", and grill it into shape a round of questions at a time, sharpening domain terms and updating
GLOSSARY.md/ADRs inline as decisions land. -
Apply the outcome:
ready-for-agent: post an agent brief comment (AGENT-BRIEF.md).ready-for-human: same structure as an agent brief, but note why it can't be delegated (judgment calls, external access, design decisions, manual testing).needs-info: post triage notes (template below).- For
wontfix, close the issue, with the comment depending on why:- Already implemented: the change already exists in the codebase. Point to where it lives; do not write to
.out-of-scope/(that KB is for rejected requests, not built ones). - Rejected (bug): give a polite explanation, then close.
- Rejected (enhancement): write to
.out-of-scope/, link to it from a comment, then close (OUT-OF-SCOPE.md).
- Already implemented: the change already exists in the codebase. Point to where it lives; do not write to
needs-triage: apply the role. Optional comment if there's partial progress.
Quick state override
If the maintainer says "move #42 to ready-for-agent", trust them and apply the role directly. Confirm what you're about to do (role changes, comment, close), then act. Skip grilling. If moving to ready-for-agent without a grilling session, ask whether they want to write an agent brief.
Needs-info template
## Triage Notes
**What we've established so far:**
- point 1
- point 2
**What we still need from you (@reporter):**
- question 1
- question 2
Capture everything resolved during grilling under "established so far" so the work isn't lost. Questions must be specific and actionable, not "please provide more info".
Resuming a previous session
If prior triage notes exist on the issue or PR, read them, check whether the reporter has answered any outstanding questions, and present an updated picture before continuing. Don't re-ask resolved questions.