What is create-pull-request?

A workflow for creating a GitHub pull request, which is a request for teammates to review and merge code changes. It finds the repository's template, base branch, and ticket reference, then prepares the request with the project's expected title and details.

Use it after making changes on a branch to prepare a normal or draft pull request. It can include ticket references, summaries of changes, testing information, effort, and difficult parts of the work.

It removes the repetitive work of checking repository conventions and assembling a complete pull request. It also helps ensure the request describes all commits and follows the project's review format.

create-pull-request — Skill by helderberto

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/helderberto/agent-skills/create-pull-request

Any agent

npx skills add helderberto/agent-skills --skill create-pull-request

Clone the repo

git clone --depth 1 https://github.com/helderberto/agent-skills

Made for: Claude Code, Codex.

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 682 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00034	$0.00682
Opus 5	$0.00017	$0.00341
Sonnet 5	$0.00007	$0.00136
Haiku 4.5	$0.00003	$0.00068

Measured 2d ago against content hash 543e7d8d7b70, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-pull-request scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/create-pull-request/SKILL.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create Pull Request

Mode: $ARGUMENTS

If --draft is passed, create as draft PR.

Workflow

Run in parallel:
- git fetch origin && git remote show origin | grep 'HEAD branch' | cut -d' ' -f5 (get base branch)
- git rev-parse --abbrev-ref HEAD | grep -oE '[A-Z]+-[0-9]+' (extract ticket ID)
- Search for PR template in order: .github/pull_request_template.md, .github/PULL_REQUEST_TEMPLATE.md, .github/PULL_REQUEST_TEMPLATE/ (directory of templates), docs/pull_request_template.md, pull_request_template.md
Run in parallel:
- git diff HEAD
- git diff [base-branch]...HEAD --unified=0
If a PR template was found, read it in full — it becomes the canonical structure for the PR body. Do not paraphrase or skip sections.
Review ALL commits (not just latest)
Ask the user (use AskUserQuestion when available; otherwise ask directly). Ask all at once where possible:
- Effort (required): how long the task took in hours (planning, reading, testing, all included)
- Changes (required): general overview of what was done
- Testing (optional): testing done that isn't visible in the diff
- Tricky parts (optional): anything hard, requiring multiple attempts, or non-obvious
- If template found, also surface any template-specific fields that can't be inferred from the diff (e.g. "Does this include breaking changes?", "What type of change is this?")
Draft title and body:
- Title must match: /^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)($.*$)?: .+$/
- If template found: use the template verbatim as the body base — fill every section/placeholder using diff + user answers; check applicable checkboxes; do NOT add sections not in the template; do NOT omit any template sections
- If no template: use Summary + Test plan
- Reference ticket ID in body if found (e.g. Resolves TICKET-123)
- Incorporate user's answers into description — don't just repeat the diff
In parallel:
- Create branch if needed
- Push with -u if needed
- Create PR with gh pr create using HEREDOC (add --draft if requested)

Read the full file on GitHub · 49 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 49 lines · 34 tokens per session scan A 543e7d8d7b70

Subscribe to this mod's changes

create-pull-request is a skill published in the GitHub repository helderberto/agent-skills (13 stars, last pushed 11d ago), licensed MIT. It adds 34 tokens to every session and 682 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review Git and workflow Testing agent-skills ai antigravity claude-code cursor skills

code-review-and-quality

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

addyosmani/agent-skills · 51 tokens

constraint-driven-development

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or…

addyosmani/agent-skills · 154 tokens

performance-optimization

Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.

addyosmani/agent-skills · 59 tokens

api-and-interface-design

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

addyosmani/agent-skills · 49 tokens

code-simplification

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.