Generates structured, validated PRs with test plans.
Install
mkdir -p .claude/skills/pr-g-zenr && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16508" && unzip -o skill.zip -d .claude/skills/pr-g-zenr && rm skill.zipInstalls to .claude/skills/pr-g-zenr
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Create a pull request with proper title, description, and test planKey capabilities
- →Run mandatory pre-PR validation (tests and type-checks)
- →Analyze the full scope of changes since branching from main
- →Generate a concise PR title (under 70 characters, imperative mood)
- →Generate a structured PR body with summary, changes, and test plan
How it works
The skill first runs tests and type-checks, ensuring they pass. It then analyzes git changes, generates a PR title and a structured PR body, and finally pushes the branch and creates the pull request on GitHub.
Inputs & outputs
When to use pr
- →Create a PR with a standard template
- →Validate code before opening a PR
- →Document test coverage in a PR body
About this skill
Create a pull request for the current branch: $ARGUMENTS
Step 1 — Pre-PR Validation
Run the test and type-check commands (see project config). Both MUST pass. Never create a PR with failing tests or type errors.
Step 2 — Analyze Changes
git log main..HEAD --oneline
git diff main...HEAD --stat
Understand the full scope of changes since branching from main.
Step 3 — Generate PR Title
- Under 70 characters
- Use imperative mood: "Add...", "Fix...", "Update..."
- Be specific about what changed
Step 4 — Generate PR Body
Use this structure:
## Summary
- Bullet point 1: what changed and why
- (1-3 bullets max)
## Changes
- List every file modified/created/deleted with brief reason
## Test Plan
- [ ] All existing tests pass
- [ ] Type checking passes
- [ ] New tests added for: <list new test coverage>
- [ ] Manual verification: <steps>
## Checklist
- [ ] Future annotations pattern followed (see stack concepts)
- [ ] Typed exceptions (no generic `Exception`)
- [ ] Typed schemas for all request/response shapes (see stack concepts)
- [ ] OpenAPI metadata on all new endpoints
- [ ] Project documentation updated (if new endpoints/config)
- [ ] Env example file updated (if new settings)
Step 5 — Push and Create PR
git push -u origin <branch-name>
gh pr create --title "<title>" --body "<body>"
Step 6 — Confirm
Output the PR URL so it can be reviewed.
When not to use it
- →When creating a PR with failing tests or type errors
- →When the user wants to skip pre-PR validation
- →When the user does not want a structured PR body
Limitations
- →Requires tests and type-checks to pass before PR creation
- →PR title is limited to under 70 characters and imperative mood
- →PR body follows a specific markdown structure
How it compares
This skill enforces mandatory pre-PR validation and generates standardized PR titles and bodies, ensuring consistency and quality before a pull request is opened, unlike manual PR creation.
Compared to similar skills
pr side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pr (this skill) | 0 | 6mo | Review | Beginner |
| code-review-checklist | 3 | 1mo | No flags | Beginner |
| openspec-verify-change | 3 | 6mo | Review | Advanced |
| superpowers-finish | 1 | 7mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
code-review-checklist
vudovn
Code review guidelines covering code quality, security, and best practices.
openspec-verify-change
studyzy
验证实现是否与变更产出物匹配。当用户想要在归档前验证实现是否完整、正确且一致时使用。
superpowers-finish
anthonylee991
Finalizes work: runs verification, summarizes changes, notes follow-ups, and ensures repo hygiene. Use at the end of an implementation or debugging session.
positron-qa-verify
posit-dev
Generates clear, actionable verification guides for QA testing of Positron bug fixes and features
categorize-revdep-issues
r-lib
Write revdep/issue.md to group packages by common error categories
pr-review
microsoft
Multi-dimensional review of a PR or feature branch in the microsoft/winappcli repo. Activate when a contributor asks to "review my PR", "review my changes", "vet my branch before pushing", "do a full review", "PR review", "review this feature", or similar. Fans out parallel sub-agents covering secur