Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →lingxling/pr-writer
Create pull requests following Sentry's engineering practices.
Passed 13 of 17 test cases with the skill, and 8 of 17 without it.
and 7 more in the full report
7 fixed10 passed either way5 still failing0 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.
I want to open a pull request for my feature branch, but I might have leftover uncommitted files in my working tree. What command should be run first to check if there are uncommitted changes before starting the PR creation workflow?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies checking uncommitted changes using git status --porcelain. | Missed | Passed |
| The response indicates that uncommitted changes must be committed before creating a PR. | Passed | Passed |
The instructions your model reads when the skill loads.
Create pull requests following Sentry's engineering practices.
Requires: GitHub CLI (gh) authenticated and available.
Before creating a PR, ensure all changes are committed. If there are uncommitted changes, run the sentry-skills:commit skill first to commit them properly.
# Check for uncommitted changes
git status --porcelain
If the output shows any uncommitted changes (modified, added, or untracked files that should be included), invoke the sentry-skills:commit skill before proceeding.
# Detect the default branch — note the output for use in subsequent commands
gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name'
# Check current branch and status (substitute the detected branch name above for BASE)
git status
git log BASE..HEAD --oneline
Ensure:
test cases passed, vs 8 / 17 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.