Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mkurman/github-triage
Triage GitHub issues through a label-based state machine.
Passed 12 of 19 test cases with the skill, and 7 of 19 without it.
and 12 more in the full report
8 fixed6 passed either way6 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are triaging issue #88, which is categorized as a bug report regarding user session timeout failures. Standard triage workflows: bug, enhancement, needs-triage, ready-for-agent, ready-for-human, wontfix. What specific step should be attempted before starting a domain model session to flesh out the issue?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies attempting to reproduce the reported bug in the codebase before initiating a domain model session. | Passed | Passed |
| Specifies reporting the reproduction attempt outcome to the maintainer. | Missed | Passed |
The instructions your model reads when the skill loads.
----------- | -------- | ---------------------------------------- |
| bug | Category | Something is broken |
| enhancement | Category | New feature or improvement |
| needs-triage | State | Maintainer needs to evaluate this issue |
| needs-info | State | Waiting on reporter for more information |
| ready-for-agent | State | Fully specified, ready for AFK agent |
| ready-for-human | State | Requires human implementation |
| wontfix | State | Will not be actioned |
Every issue should have exactly one state label and one category label. If an issue has conflicting state labels (e.g. both needs-triage and ready-for-agent), flag the conflict and ask the maintainer which state is correct before doing anything else. Provide a recommendation.
| Current State | Can transition to | Who triggers it | What happens |
|---|---|---|---|
unlabeled | needs-triage | Skill (on first look) | Issue needs maintainer evaluation. Skill applies label after presenting recommendation. |
unlabeled | ready-for-agent | Maintainer (via skill) | Issue is already well-specified and agent-suitable. Skill writes agent brief comment, applies label. |
unlabeled | ready-for-human | Maintainer (via skill) | Issue requires human implementation. Skill writes a brief comment summarizing the task, applies label. |
unlabeled | wontfix | Maintainer (via skill) | Issue is spam, duplicate, or out of scope. Skill closes with comment (and writes .out-of-scope/ for enhancements). |
needs-triage | needs-info | Maintainer (via skill) | Issue is underspecified. Skill posts triage notes capturing progress so far + questions for reporter. |
needs-triage | ready-for-agent | Maintainer (via skill) | Grilling session complete, agent-suitable. Skill writes agent brief comment, applies label. |
needs-triage | ready-for-human | Maintainer (via skill) | Grilling session complete, needs human. Skill writes a brief comment summarizing the task, applies label. |
needs-triage | wontfix | Maintainer (via skill) | Maintainer decides not to action. Skill closes with comment (and writes .out-of-scope/ for enhancements). |
needs-info | needs-triage | Skill (detects reply) | Reporter has replied. Skill surfaces to maintainer for re-evaluation. |
An issue can only move along these transitions. The maintainer can override any state directly (see Quick State Override below), but the skill should flag if the transition is unusual.
The maintainer invokes /github-triage then describes what they want in natural language. The skill interprets the request and takes the appropriate action.
Example requests:
test cases passed, vs 7 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.