Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →testdouble/update-pr-description
Generate a PR description from the current branch's changes against a GitHub PR, using the gh CLI.
Passed 6 of 13 test cases with the skill, and 4 of 13 without it.
and 6 more in the full report
6 fixed5 passed either way12 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
What must be the exact first line immediately following the `## Summary` heading in Option A (no template)?
| Checked | Without skill | With skill |
|---|---|---|
| Requires the first line under ## Summary to be the bolded TL;DR sentence. | Missed | Passed |
The instructions your model reads when the skill loads.
which gh 2>/dev/null || echo "not installed"If the gh CLI is not found:
git branch --show-current 2>/dev/null || echo unknowngit symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || echo unknowngit log origin/HEAD..HEAD --oneline 2>/dev/null || echo unknowngit diff origin/HEAD...HEAD --stat 2>/dev/null || echo unknowngit diff origin/HEAD...HEAD 2>/dev/null || echo unknownbash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"cat .han/config.md 2>/dev/null || echo ""As your first action, use the Read tool on .han/config.md inside the personal config directory path above. A read
that returns no file is no personal configuration: continue silently. When that file or the project .han/config.md
probe supplies content, apply it per config-rule.md, which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
Before generating a PR description, verify the branch has content to describe:
If default branch is empty or unknown — origin/HEAD is not set. Use AskUserQuestion to ask the user for
the default branch name (e.g., main, master, develop). Use that branch as the base for all git commands in
subsequent steps, and recompute branch summary, branch stats, and branch changes against it — their Project
Context values may read unknown because they were derived from the unset origin/HEAD.
If branch summary is empty — there are no commits on this branch relative to the default branch. Inform the
user and stop.
If branch stats is empty — there are no file changes despite having commits (e.g., empty commits or fully
reverted changes). Inform the user and stop.
test cases passed, vs 4 / 13 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.