pr
Commit, push, and open a pull request. Use when finished work on the current branch needs to become a PR.
- Installs
- 79
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/owainlewis/blueprint --skill pr- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads pr automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
PR
- If still on the default branch, create or switch to a task branch first.
- Commit intended changes with a Conventional Commit subject. Stage only intended files.
- Before writing the PR body, read the repo's PR template if one exists. Check
.github/pull_request_template.md,.github/PULL_REQUEST_TEMPLATE.md,pull_request_template.md,docs/pull_request_template.md, and.txtvariants. If aPULL_REQUEST_TEMPLATE/directory exists under.github/, the repo root, ordocs/, pick the template named by the repo or user; otherwise use the default template if present. - Push and open the PR, ready for review by default, draft only when asked or the work is known incomplete. Title reads like a commit subject: in squash-merge repos it becomes the commit on the default branch.
- Write the body from the template when one exists. Preserve headings and fill relevant sections from the diff and work done: what changed and why, ticket link when one exists, checks run with results, review issues fixed, and anything not checked. If no template exists, write a concise body with those same details.
- Report the PR URL.
Rules
- One PR per branch. If one is open, push and update it. Preserve human edits to the body: update only what the new commits change.
- Follow the repo's PR template when one exists.
- Never claim checks that did not run.
- If push or PR creation fails, keep the work local and report the exact failure.
FAQ
What does the pr skill do?
Commit, push, and open a pull request. Use when finished work on the current branch needs to become a PR.
How do I install pr?
Run npx skills add https://github.com/owainlewis/blueprint --skill pr in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/pr/ (personal) or .claude/skills/pr/ (project).
Which AI agents can use pr?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is pr safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains pr?
It is published by owainlewis in owainlewis/blueprint. It has 79 recorded installs.
More from owainlewis/blueprint
review
owainlewis/blueprint
Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, and missing proof. Use for code, PR, diff, security, second-opinion, or pre-merge reviews.
plan
owainlewis/blueprint
Turns a reviewed spec or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.
task-to-pr
owainlewis/blueprint
Open the skill to read its SKILL.md instructions.
spec
owainlewis/blueprint
Open the skill to read its SKILL.md instructions.
refactor
owainlewis/blueprint
Improve the shape of existing code without changing behavior.
Popular code quality & workflow skills
grill-me
mattpocock/skills
A relentless interview to sharpen a plan or design.
improve-codebase-architecture
mattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
handoff
mattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
domain-modeling
mattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
codebase-design
mattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.