Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/update-pr
Update an existing GitHub pull request's title and description to reflect the current state of the branch.
Passed 7 of 16 test cases with the skill, and 6 of 16 without it.
and 2 more in the full report
5 fixed5 passed either way9 still failing4 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.
We are drafting a new title for a pull request that describes multiple refactors in the authentication service. What is the maximum character limit for the pull request title?
| Checked | Without skill | With skill |
|---|---|---|
| Enforces a title limit of 72 characters or fewer | Missed | Passed |
The instructions your model reads when the skill loads.
Read the current PR title and body, analyze what changed in the session, and draft an updated title and description that preserves the original writing style.
Fetch the current PR details:
gh pr view [PR_NUMBER] --json number,title,body,baseRefName,headRefName,updatedAt,commits
Omit PR_NUMBER to auto-detect from current branch.
Before drafting, study the current title and body to identify:
feat:, fix:), capitalizationUse the PR's updatedAt field and commit timestamps to determine whether new commits were added since the body was last edited.
If commits_since_body_change is empty, the description is already up to date — say so and stop.
Run git fetch origin <base> so the remote ref is current before any diff below. A local branch of the same name can sit behind the remote, which puts the merge base before an already-merged pull request and pulls merged work into the description.
If there are commits since the last body change, check the incremental diff to assess significance:
git diff origin/<base>...HEAD --diff-filter=d --stat -- $(git log --since="<body_last_changed>" --name-only --pretty=format: origin/<base>..HEAD | sort -u)
Skip the update if the incremental changes are trivial (formatting, typos, config-only). Proceed if they add, remove, or modify meaningful behavior.
test cases passed, vs 6 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.