What is create-pull-request?

A workflow for opening a GitHub pull request, which is a proposal to merge code into a project repository. It uses a product-focused title and detailed description based on the branch’s changes.

Use it when asked to push a branch or open a pull request. It checks the status and diff, confirms verification and review, and prepares the required pull-request sections.

It gives reviewers enough context to understand the problem, the change, and how it was checked. It also keeps internal workflow details out of the public pull request.

create-pull-request — Skill for Claude Code and Codex by David405

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.

Any agent

npx skills add David405/harness-kit --skill create-pull-request

Clone the repo

git clone --depth 1 https://github.com/David405/harness-kit

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/david405/harness-kit/create-pull-request/github.svg)](https://agentmods.dev/skills/david405/harness-kit/create-pull-request)

Your own site

<a href="https://agentmods.dev/skills/david405/harness-kit/create-pull-request"><img src="https://agentmods.dev/badge/skills/david405/harness-kit/create-pull-request/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/david405/harness-kit/create-pull-request"><img src="https://agentmods.dev/badge/skills/david405/harness-kit/create-pull-request.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00070	$0.00712
Opus 5.5	$0.00028	$0.00285
Sonnet 5.5	$0.00014	$0.00142
Haiku 4.5	$0.00007	$0.00071

Measured 2mo ago against content hash de9f3f354d69, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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 · 100 lines

How it starts

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

Create pull request

GitHub PRs are product-facing and detailed. A reviewer who has not seen the session should understand the problem, the fix, what changed in behaviour, and how it was verified. Harness workflow (contracts, FEATURES.json IDs, harness-review, audit finding codes) stays in local/session context only.

Before opening

Human explicitly asked to push and/or open a PR.
VERIFY is green; harness review is done (reported in chat, not in the PR body).
Run git status, git diff vs the default branch, git log for commits on the branch.
Draft the full body from the diff — do not ship a sparse PR.

Title format

Conventional commit style — no ticket/harness IDs:

<type>(<scope>): <what changed in plain English>

Do not include: feature ledger IDs (SEC-002, PAY-015), audit codes (AUDIT-001-F02), PENDING_REVIEW, or contract file paths.

Body template (required sections)

Use all sections below. Omit a section only when truly N/A (say "N/A" in one line).

Template file: templates/pull_request_template.md (install to .github/pull_request_template.md via setup-harness-kit.sh when missing).

## Summary

<2–4 sentences: what this PR does and why it matters.>

## Problem

<What was broken, unsafe, or missing — user-visible or production symptom.>

## Solution

<How the code fixes it. Key functions, routes, guards.>

## Behaviour changes

| Before | After |
|--------|-------|
| <old> | <new> |

## Files changed

- `path/to/file` — <one line each>

## Risk and rollout

- **Risk:** Low / Medium / High — <why>
- **Rollback:** <safe to revert?>
- **Prod / env notes:** <env vars, flags — or "None">

## Test plan

- [x] `<command>` — <result>
- [ ] CI build + e2e

Forbidden in title, body, and commit messages

Feature ledger IDs, audit finding IDs, contract paths
Sections named "Harness review", "Contract compliance", sprint contract paste
Contract HTML markers ()
Tool attribution (Made with Cursor, Co-Authored-By assistant)

Read the full file on GitHub · 100 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

templates/pull_request_template.md 251 B

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.

2mo ago First seen · 100 lines · 70 tokens per session scan A de9f3f354d69

Subscribe to this mod's changes

create-pull-request is a skill published in the GitHub repository David405/harness-kit (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 70 tokens to every session and 712 once invoked, about $0.0003 per session on Opus 5.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-31.

Git and workflow

create-pull-request

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Create pull request

Before opening

Title format

Body template (required sections)

Forbidden in title, body, and commit messages

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

merge-batch

prowler-commit

gh-auth-isolation

comet-github

github-skill

release-helper