Move issues and external PRs through a triage state machine with categorization and agent-ready briefs.
npx skills add https://github.com/peachest/skills --skill triage-peachest
Please help me install this Agent Skill. Skill: triage Source: https://github.com/peachest/skills/tree/main/vendor/mattpocock/skills/engineering/triage Command: npx skills add https://github.com/peachest/skills --skill triage-peachest
.out-of-scope/ knowledge base for rejected feature requests. - Use Case: A maintainer asks "Show me anything that needs my attention" and receives three buckets (unlabeled, needs-triage, needs-info with new reporter activity), then picks issue #42, gets a category and state recommendation backed by codebase checks, and moves it to ready-for-agent with a posted brief. ## Quick Start Ask the agent to triage issue #42 by gathering its context, verifying the claim against the codebase, and recommending a category and state.High-intent search queries and answers about installing and using this skill.
Invoke the triage skill with a natural language request like "Let's look at #42". The skill reads the full issue, checks the codebase for redundancy and prior rejections, verifies the claim, and recommends a category and state role before applying labels and comments.
An agent brief is a structured comment posted when an issue moves to ready-for-agent, serving as the authoritative spec for an AFK agent. It describes desired behavior, key interfaces, testable acceptance criteria, and explicit out-of-scope boundaries without referencing fragile file paths or line numbers.
Yes, when the issue tracker config treats external PRs as a request surface, a PR is triaged as an issue with attached code using the same roles and states. The skill additionally checks out the diff and runs relevant tests to confirm it does what it claims.
Rejected enhancement requests are recorded as concept files in .out-of-scope/ with the decision, reasoning, and prior issue links. During triage, new issues are matched against these files by concept similarity so prior rejections are surfaced instead of re-litigated.
Use ready-for-human when the work cannot be delegated to an agent, such as judgment calls, external access requirements, design decisions, or manual testing. The skill posts the same brief structure but notes why human implementation is required.
probationer070Configure engineering skills with issue tracker, triage labels, and domain documentation.
githubDrives open pull requests to merge-ready state by resolving reviews, validating locally, and fixing mergeability.
mikalvRuns a structured design interview that produces ADRs and a glossary.
linaproaiTriage community GitHub issues for the LinaPro project with labels and comments.