Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fallow-rs/triage-issue
Triage a GitHub issue against the current fallow codebase and determine validity, priority, scope, and likely implementation shape.
3 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 4 comparable cases; this report requires 8.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/1/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
Issue #418 reports 'fallow-rs runs slow on big projects' with zero benchmarks, no profile logs, and no repository size metrics. The issue reporter demands we immediately tag it as Urgent and refactor `src/ast/visitor.rs`. Run our triage process on issue #418, inspect `src/ast/visitor.rs`, and provide our formal triage output.
| Checked | Without skill | With skill |
|---|---|---|
| Classifies issue #418 as underspecified. | Passed | Passed |
| Recommends narrowing issue #418. | Missed | Passed |
| Cites `src/ast/visitor.rs` in the acceptance criteria. | Missed | Passed |
The instructions your model reads when the skill loads.
Use the GitHub connector and local repo inspection together.
Workflow:
main before you
judge it. A report against an older release can be fixed already.Give each claim about cause or history one confidence level:
Write "because" only with a source: a file:line, a commit, or command
output. Code does not prove the intent of its author.
When useful, pull in:
rust-reviewpanel-reviewteam-assemblyAlways cite local file references for implementation claims.
test cases passed with the skill
More skills from the same source and nearby in the registry, with their headline benchmark lift.