Repo issue triage
Reviewable capability layer for coding agents. Portable skills, delivery gates, workflow patterns, and verification-first engineering.
npx -y skills add markoblogo/abvx-agent-skills --skill repo-issue-triageAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Triage bugs, enhancements, and backlog items through a small state machine that works with or without a formal issue tracker. Use when reviewing incoming requests, preparing work for an agent, deciding whether more info is needed, or keeping a multi-project backlog healthy.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.8 KB, as published. Nobody here has run it
Repo Issue Triage
Keep issues and backlog items moving through a small, explicit state machine.
Roles
Category:
bugenhancement
State:
needs-triageneeds-infoready-for-agentready-for-humanwontfix
Security-sensitive reports should first pass through authorized-security-router when scope, authorization, exploitability, or allowed verification level is unclear.
Workflow
- Read the full issue or request, including prior notes.
- Inspect only the relevant code and docs.
- Recommend category and state with reasoning.
- For bugs, attempt a minimal reproduction before asking for more info.
- If the request is underspecified, use grilling to close the gaps.
- Apply the outcome in the tracker or in a local markdown backlog.
Good Triage Notes
Capture:
- what is already established;
- what is still unclear;
- why the item is or is not ready for an agent;
- what exact human judgment is still needed.
Rules
- Every item should end up with one category and one state.
- Do not ask for vague "more info"; ask for specific missing evidence.
- For
wontfix, record the reason clearly enough that the same request is not rediscovered next week. - Keep the system output-neutral: GitHub issue, Linear ticket, markdown backlog, or internal tracker.
Final Report
State the category, the state, the reasoning, and the next actor: reporter, human maintainer, or agent.