Create a GitHub pull request. Use when the user asks to open, create, or submit a PR, when work is ready for review, or whenever gh pr create would otherwise be run.
Scanned 9/10/2026
Install to Claude Code
npx -y skills add staticaland/skills --skill create-pr --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Create Pr?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/staticaland-create-pr)More formats (shields.io, HTML) on the badges page.
---
name: create-pr
description: >
Create a GitHub pull request. Use when the user asks to open, create, or
submit a PR, when work is ready for review, or whenever gh pr create would
otherwise be run.
---
# create-pr
Open a PR whose description lets a reviewer judge the change without having
been in the session.
## Steps
1. Run `<skill-dir>/scripts/pr.py prepare`, where `<skill-dir>` is this
skill's base directory. It pushes the branch, prints the template to fill,
and prints the `BODY FILE:` path it created for this run.
2. Fill every template section from the whole session, not the diff alone: the
original request, the decisions made and their tradeoffs, and what was
tested and how. Follow the writing instructions in the template's comments,
and leave the comments in place - the submit step removes them.
3. Read the `BODY FILE:` path `prepare` printed with the Read tool - the file
is an empty placeholder, and the Write tool refuses a file it has not read.
Then write the filled template to that exact path - never a path of your
own choosing, which risks reusing a stale body from an earlier session.
Then run:
```bash
<skill-dir>/scripts/pr.py submit "<title>" <body-file>
```
The submit command strips the comments and creates the PR through `gh`; the
guard hook blocks a bare `gh pr create`.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.
Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.
Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.
一个全面的 Claude Code 会话验证系统。
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.