Automates the creation of pull requests with standardized PR bodies and test plans.
Install
mkdir -p .claude/skills/pr-buddiesofbudgie && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11911" && unzip -o skill.zip -d .claude/skills/pr-buddiesofbudgie && rm skill.zipInstalls to .claude/skills/pr-buddiesofbudgie
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 for the current branchKey capabilities
- →Gather current git status and commit history
- →Determine the conventional commit prefix based on changes
- →Generate a PR title and body following a specific format
- →Push the current branch to origin
- →Create a pull request against the `main` branch
- →Include a test plan checklist in the PR description
How it works
The skill gathers git context, determines the PR type, generates formatted PR content including a test plan, and then pushes the branch and creates the pull request.
Inputs & outputs
When to use pr
- →Create PR for current feature
- →Automate PR description generation
- →Verify tests before pushing PR
About this skill
Create a Pull Request
You are creating a pull request for the current branch on Buddies of Budgie docs (Docusaurus / React / TypeScript site).
Step 1: Gather Context
Run these commands to understand the current state:
git status
git log --oneline main..HEAD
git diff main...HEAD --stat
git diff main...HEAD
git branch --show-current
If there are uncommitted changes, run the /commit skill first before proceeding.
Step 2: Determine PR Type
Based on the changes, choose the conventional commit prefix:
feat:- New feature or functionalityfix:- Bug fixchore:- Maintenance, dependency updates, refactoringdocs:- Documentation content changesrefactor:- Code restructuring without behavior change
Step 3: Generate PR Content
Title format: <type>: <short description> (under 70 characters)
Body format:
## Summary
- <bullet point describing key change 1>
- <bullet point describing key change 2>
- <bullet point describing key change 3>
## Test plan
- [ ] `yarn build` completes successfully
- [ ] `yarn typecheck` passes
- [ ] `yarn lint` passes
- [ ] Verified locally with `yarn start`
- [ ] <additional specific test steps>
If any commits include Assisted-by trailers, note that in the PR description (e.g., "AI-assisted - see commit trailers for details").
Step 4: Create the PR
Push the branch and create the PR:
git push -u origin HEAD
gh pr create --title "<title>" --body "$(cat <<'EOF'
<body content>
EOF
)"
Target branch: main (default)
Notes
- Review all commits since divergence from main, not just the latest one
- Ensure the title accurately reflects the overall change
- Test plan should include
yarn build,yarn typecheck, andyarn lint
When not to use it
- →When there are uncommitted changes in the working directory
- →When the target branch is not `main`
- →When the project is not a Docusaurus / React / TypeScript site
Prerequisites
Limitations
- →Uncommitted changes require running the `/commit` skill first.
- →The target branch for the PR is `main` by default.
- →The generated test plan includes specific `yarn` commands relevant to the project.
How it compares
This skill automates the creation of pull requests with predefined formatting and a test plan, ensuring consistency for Buddies of Budgie docs, 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 | 4mo | Review | Beginner |
| accessibility-compliance | 45 | 2mo | No flags | Intermediate |
| typescript | 28 | 2mo | No flags | Beginner |
| frontend-code-review | 11 | 2mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
accessibility-compliance
wshobson
Implement WCAG 2.2 compliant interfaces with mobile accessibility, inclusive design patterns, and assistive technology support. Use when auditing accessibility, implementing ARIA patterns, building for screen readers, or ensuring inclusive user experiences.
typescript
lobehub
TypeScript code style and optimization guidelines. Use when writing TypeScript code (.ts, .tsx, .mts files), reviewing code quality, or implementing type-safe patterns. Triggers on TypeScript development, type safety questions, or code style discussions.
frontend-code-review
langgenius
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.
react-best-practices
redpanda-data
Client-side React performance optimization patterns.
react-patterns
davila7
Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices.
coding-standards
affaan-m
适用于TypeScript、JavaScript、React和Node.js开发的通用编码标准、最佳实践和模式。