Install any skill in seconds. Free to start, no credit card required.
Get Started Free →jnmetacode/pr-description
Write a reviewer-first pull-request description from the actual branch diff.
Passed 17 of 22 test cases with the skill, and 13 of 22 without it.
and 4 more in the full report
5 fixed12 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
I spent 3 days discussing redis caching strategies in Slack before making a simple diff in `cache.go` setting TTL to 300 seconds for repository `acme/cache-service`. Write the opening sentence for the pull request.
| Checked | Without skill | With skill |
|---|---|---|
| The opening states the concrete problem without summarizing past Slack conversation history. | Missed | Passed |
The instructions your model reads when the skill loads.
The reader is a reviewer deciding how to review, not a historian. Write from the diff, not from memory of the conversation.
git log main..HEAD --oneline and
git diff main...HEAD --stat. Read the diff of every file a reviewer will
question.Fixes checkout failing for SSO users (#412).
**What**
- Treat IdP-initiated sessions as authenticated in the cart guard (behavior)
- Extract session checks into `session.ts` (refactor, no behavior change)
**Verify**: `npm test` (all green) + manual SSO login → add to cart → checkout.
test cases passed, vs 13 / 22 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.