Enforces project-wide PR standards and testing requirements.
Install
mkdir -p .claude/skills/pr-pluginslab && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11921" && unzip -o skill.zip -d .claude/skills/pr-pluginslab && rm skill.zipInstalls to .claude/skills/pr-pluginslab
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 branch, description, and labelsKey capabilities
- →Create feature branches
- →Run unit tests
- →Run JavaScript linting
- →Run PHP linting
- →Create GitHub pull request with structured body
- →Add labels to pull request
How it works
The skill first ensures that unit tests and linting checks pass. If not on a feature branch, it creates one. Then, it creates a GitHub pull request with a specified title, a structured body, and relevant labels.
Inputs & outputs
When to use pr
- →Create pull request
- →Submit code changes
- →Enforce test pass before PR
About this skill
Create Pull Request
Branch naming
If not already on a feature branch, create one from the commit history:
- Features:
feature/<short-description> - Fixes:
fix/<short-description> - Docs:
docs/<short-description> - Refactors:
refactor/<short-description>
Pre-flight checks
- Run
npm test— unit tests must pass - Run
npx wp-scripts lint-json changed JS files - Run
composer lintif PHP files changed - Check
git diff main...HEADto understand full scope of changes
Create the PR
Base branch: $ARGUMENTS (default: main)
Use gh pr create with:
- Title: under 70 chars, imperative mood (e.g., "Add cron-list ability" not "Added cron-list ability")
- Body format:
## Summary
<2-4 bullet points describing what changed and why>
## Changes
<list of files/areas affected>
## Testing
- [ ] Unit tests pass (`npm test`)
- [ ] Ability tests pass (`npm run test:abilities -- --file tests/abilities/core-abilities.test.js`)
- [ ] JS lint clean (`npm run lint:js`)
- [ ] PHP lint clean (`composer lint`)
- [ ] Manually tested in browser (if UI changes)
## Notes
<any migration steps, breaking changes, or reviewer guidance>
- Labels: add if available —
enhancement,bug,documentation,breaking-change - Push branch with
-uflag before creating PR
After creating
Print the PR URL so the user can review it.
When not to use it
- →When unit tests do not pass
- →When JavaScript linting is not clean
- →When PHP linting is not clean
Limitations
- →Unit tests must pass
- →JS lint clean
- →PHP lint clean
How it compares
This skill enforces pre-flight checks like unit tests and linting before creating a pull request, ensuring code quality standards are met automatically.
Compared to similar skills
pr side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pr (this skill) | 0 | 5mo | Review | Beginner |
| dependency-upgrade | 26 | 5mo | Review | Intermediate |
| woocommerce-email-editor | 3 | 6mo | Review | Advanced |
| validate-typescript | 5 | 9mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
dependency-upgrade
wshobson
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing. Use when upgrading framework versions, updating major dependencies, or managing breaking changes in libraries.
woocommerce-email-editor
woocommerce
Setup and develop the WooCommerce block email editor. Use when working on email templates, transactional emails, or the email editor feature.
validate-typescript
BerryKuipers
Run TypeScript compiler type-checking (tsc --noEmit) to validate type safety and catch type errors. Works with any TypeScript project. Returns structured output with error counts, categories (type/syntax/import errors), and affected files. Used for quality gates and pre-commit validation.
ts-testing
johnlindquist
Design, implement, and maintain high‑value TypeScript test suites using popular JS/TS testing libraries. Use this skill whenever the user is adding tests, debugging failing tests, or refactoring code that should be covered by tests.
react-best-practices
redpanda-data
Client-side React performance optimization patterns.
feature-flags
Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging channel-specific test failures, or adding new flags to React.