pull-request — Claude Code skill: PRs and setup
This skill keeps pull requests clear and reviewable, from issue links and scope splits to CI, feedback, and merge readiness.
npx skills add wendylabsinc/claude-skills --skill pull-request -a claude-codeWhat pull-request does
The skill helps maintain a pull request as a current record of the branch. It guides the agent through choosing the right issue relationship, describing the delivered behavior, recording validation, and keeping commit history and contributor attribution intact. It also helps decide when work should become several related PRs instead of one mixed change.
It checks durable boundaries such as database schemas, REST and gRPC APIs, public SDKs, user interfaces, and command-line tools. For those changes, the description should state the observable contract difference, compatibility impact, and affected consumers. The skill also covers CI and review feedback. Repository-specific guidance takes precedence, so read the contributor rules, PR template, required checks, and merge policy before making changes. Pushing, opening a draft, marking a PR ready, and merging are treated as separate authorized actions.
What it helps with
- write a PR description from the current diff
- link a pull request to an issue or PR stack
- split work by risk and contract boundaries
- document REST, SDK, CLI, or schema changes
- check whether a PR is ready for review and merge
Example prompts for the agent
- Write a concise pull request description from the current diff, with a summary and tests section.
- Decide whether these changes should be split into several PRs, then choose the true issue relationship.
- Inspect the REST API changes and describe the observable before-and-after contract for consumers.
How to install pull-request
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill pull-request -a claude-code2Manually: put the files in place
~/.claude/skills/pull-request/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/pull-request/
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill pull-request -a codex2Manually: put the files in place
.agents/skills/pull-request/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill pull-request -a cursor2Manually: put the files in place
.cursor/skills/pull-request/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install wendylabsinc/claude-skills pull-request2Manually: put the files in place
.github/skills/pull-request/SKILL.md1Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill pull-request -a gemini-cli2Platform CLI
gemini skills install https://github.com/wendylabsinc/claude-skills --path pull-requestManually: put the files in place
.devin/skills/pull-request/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add wendylabsinc/claude-skills --skill pull-request -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about pull-request
How do I install pull-request in Claude Code?
Run npx skills add wendylabsinc/claude-skills --skill pull-request -a claude-code, then check ~/.claude/skills/pull-request/SKILL.md.
What does the pull-request skill do?
It helps create and maintain reviewable PRs, connect them to issues, split related work, document contract changes, and track CI, review feedback, and merge readiness.
Which changes need a separate boundary section in a PR?
Changes to database schemas, REST or gRPC APIs, public SDKs, UIs, or CLIs need one when they alter an external contract. Describe the observable delta, compatibility impact, and affected consumers.
