Opens GitHub PRs targeted to main using pre-configured repository templates.
Install
mkdir -p .claude/skills/pr-evermind-ai && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17307" && unzip -o skill.zip -d .claude/skills/pr-evermind-ai && rm skill.zipInstalls to .claude/skills/pr-evermind-ai
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.
Open a GitHub PR targeting the correct branch with the project templateKey capabilities
- →Confirm base and head branches for the PR
- →Ensure local CI checks pass before PR creation
- →Create a PR using `gh pr create` with a template
- →Fill out PR template sections like Summary, Area, Verification, Checklist, Notes for Reviewers
How it works
The skill creates a GitHub Pull Request by first validating the branch state and local CI checks, then pushing the branch, and finally using the `gh pr create` command to open the PR with the project template.
Inputs & outputs
When to use pr
- →Creating new PRs
- →Running CI before PR submission
- →Following PR templates
About this skill
/pr
Open a pull request on GitHub using the gh CLI and the repo's PR template.
Steps
- Confirm the branch and target:
- Base branch is
main. - Head branch should be a scoped branch such as
feat/*,fix/*,docs/*,ci/*,chore/*, orrefactor/*.
- Base branch is
- Ensure local checks pass first:
Do not open a PR with failing lint/tests.make ci - Push the branch:
git push -u origin HEAD - Create the PR, filling the template
(.github/PULL_REQUEST_TEMPLATE.md):
Then edit the body to complete each section:gh pr create --base main --fill-first- Summary — what changed and why.
- Area — tick the relevant box (architecture / benchmark / use case / docs / DX / CI-build-release).
- Verification — paste the commands you ran (
make ci, manual checks). - Checklist — tick honestly; don't tick boxes you didn't satisfy.
- Notes for Reviewers — anything subtle.
Notes
- Keep the PR scoped to one area. Split unrelated changes.
- If
make ciwas not fully run, say so in Verification rather than implying it passed. - Never retarget a community PR away from
mainunless a maintainer explicitly asks for it.
When not to use it
- →When the branch contains multiple independent logical changes that should be split
- →When local CI checks are failing
- →When the goal is not to open a GitHub PR
Limitations
- →Does not allow opening a PR with failing lint/tests
- →Requires the PR to be scoped to one area; unrelated changes must be split
- →Does not allow retargeting a community PR away from `main` without maintainer request
How it compares
This skill automates the PR creation process by enforcing branch naming conventions, pre-checking CI, and guiding the user through filling a standardized template, making it more consistent than manual PR submission.
Compared to similar skills
pr side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| pr (this skill) | 0 | 29d | Review | Beginner |
| github-workflow-automation | 11 | 2mo | Review | Advanced |
| testing-workflow | 16 | 9mo | Review | Intermediate |
| github-actions-templates | 7 | 3mo | No flags | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
github-workflow-automation
ruvnet
Advanced GitHub Actions workflow automation with AI swarm coordination, intelligent CI/CD pipelines, and comprehensive repository management
testing-workflow
amo-tech-ai
Comprehensive testing workflow for E2E, integration, and unit tests. Use when testing applications layer-by-layer, validating user journeys, or running test suites.
github-actions-templates
wshobson
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
glab
NikiforovAll
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
create-pr
n8n-io
Creates GitHub pull requests with properly formatted titles that pass the check-pr-title CI validation. Use when creating PRs, submitting changes for review, or when the user says /pr or asks to create a pull request.
gh-fix-ci
openai
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use `gh` to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.