Triage Issue
Triage a GitHub issue against the current fallow codebase and determine validity...
Install
npx skills add fallow-rs/fallow --skill triage-issue -g -a claude-code -y- Repository
- fallow-rs/fallow5.3k
- Category
- Git and review
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 269 tokens
- Runs scripts
- No, instructions only
What it does
Triage a GitHub issue against the current fallow codebase and determine validity, priority, scope, and likely implementation shape. Use when the user asks to triage an issue, assess a bug report, or evaluate an enhancement request.
Triage Issue
Use the GitHub connector and local repo inspection together.
Workflow:
- Fetch the issue and comments.
- Reproduce the report on a binary built from current
mainbefore you judge it. A report against an older release can be fixed already. - Inspect the relevant code paths locally.
- Determine whether the issue is valid, overstated, underspecified, or already covered.
- Recommend priority and whether the issue should be kept, split, narrowed, or closed.
- Give acceptance criteria tied to the current codebase.
Give each claim about cause or history one confidence level:
- direct: you ran it, or the source shows it;
- supported: two independent sources agree;
- inferred: it follows from the evidence, but nothing shows it;
- speculative: plausible, with no evidence;
- unknown.
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-assembly
Always cite local file references for implementation claims.
