Our review
Creates a structured pull request with title, description, and test plan, after automatically validating tests and type checks.
Strengths
- Automatic validation of tests and type checks before PR creation
- Complete and standardized PR structure (title, summary, changes, test plan)
- Integrates project-specific compliance checklist directly
Limitations
- Depends on the project's test and type-check configuration
- Only works with GitHub (uses gh command)
- Assumes the base branch is 'main'
Use this skill when you need to create a pull request for a feature or fix branch.
Do not use it for repositories not hosted on GitHub or with highly customized PR workflows.
Security analysis
SafeThe skill uses only standard development tools (git, gh) for non-destructive operations (git log, git diff, git push, gh pr create). No risky commands or exfiltration; it's a typical PR creation workflow.
No concerns found
Examples
Create a pull request for the current branchCreate a pull request for my-branch with title 'Add user authentication'name: pr description: Create a pull request with proper title, description, and test plan disable-model-invocation: true
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.
Next.js App Router Expert
Development
A skill that turns Claude into a Next.js App Router expert.
README Generator
Development
Creates professional and comprehensive README.md files for your projects.
API Documentation Writer
Development
Generates comprehensive API documentation in OpenAPI/Swagger format.