Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fallow-rs/address-pr-comments
Triage and address GitHub PR review feedback for fallow, then implement the agreed fixes.
Passed 10 of 17 test cases with the skill, and 9 of 17 without it.
and 4 more in the full report
6 fixed8 passed either way5 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.6-flash on 10/4/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
I updated crates/parser/src/lib.rs based on review feedback on PR #310. Should I execute the full workspace test suite cargo test --workspace or a specific package test cargo test -p parser?
| Checked | Without skill | With skill |
|---|---|---|
| The response selects cargo test -p parser. | Missed | Passed |
The instructions your model reads when the skill loads.
Use GitHub review metadata plus the local checkout.
Workflow:
docs/development/quality-gates.md.Follow repo conventions from AGENTS.md: no AI attribution, signed commits when committing.
test cases passed, vs 9 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.