Moves GitHub issues and external PRs through a triage state machine with agent-ready briefs.
npx skills add https://github.com/j172/bid --skill triage-j172
Please help me install this Agent Skill. Skill: triage Source: https://github.com/j172/bid/tree/main/agent/skills/triage Command: npx skills add https://github.com/j172/bid --skill triage-j172
.out-of-scope/ knowledge base so rejected feature requests are never re-litigated. - Use Case: A maintainer asks what needs attention; the Skill lists unlabeled, in-progress, and reporter-replied items, then walks issue #42 through codebase redundancy checks, verification, and a posted agent brief. ## Quick Start Ask the assistant to triage issue #42 on the repository and recommend a category and state with reasoning.High-intent search queries and answers about installing and using this skill.
Invoke the triage workflow with a natural language request such as looking at a specific issue number or listing items needing attention. The assistant reads the issue, checks the codebase for existing implementations, verifies claims, and recommends a category and state.
Use one category label (bug or enhancement) and one state label (needs-triage, needs-info, ready-for-agent, ready-for-human, or wontfix) per issue. The actual label strings can differ from these canonical role names through a configured mapping.
Yes, external pull requests are treated as issues with attached code and move through the same states. For a PR, verification means checking out the diff and running relevant tests, and ready-for-agent means an agent should continue work on the existing diff.
A good agent brief describes behavioral contracts and acceptance criteria rather than file paths or line numbers, which go stale. It states current behavior, desired behavior, key interfaces, testable criteria, and explicit out-of-scope boundaries.
Record rejected enhancements in an out-of-scope knowledge base file with the decision, reasoning, and links to prior requests. Do not record bugs or features closed because they are already implemented, since those are not rejections.
OutlineDrivenApply configurable label-based state machines to triage GitHub issues.
mambo-wangMove GitHub issues and external PRs through a triage state machine with agent-ready briefs.
mikalvRuns a structured design interview that produces ADRs and a glossary.
BluMintIncAutomate triaging, labeling, and maintenance workflows for the eslint-custom-rules repository.