github-pull-request

github-pull-request is a skill for Claude Code, Codex from fmind/dot. It costs 39 tokens per session (685 once invoked), scanned A, original, MIT.

A guide for creating or updating GitHub pull requests, which are proposed code changes submitted for review, with a consistent summary and test plan.

In plain words
What is it for?
Use it to inspect branch changes and prepare a pull request describing what changed, why it changed, how it works, and how it was tested.
Why use it?
It prevents changes from being opened from the wrong branch and ensures the request reflects the actual code, tests, and review context.

Skill for Claude CodeCodex

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/fmind/dot/github-pull-request
Any agent
npx skills add fmind/dot --skill github-pull-request
Clone the repo
git clone --depth 1 https://github.com/fmind/dot

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.

agentmods badge for github-pull-request

README.md
[![agentmods](https://agentmods.dev/badge/skills/fmind/dot/github-pull-request.svg)](https://agentmods.dev/skills/fmind/dot/github-pull-request)
Your own site
<a href="https://agentmods.dev/skills/fmind/dot/github-pull-request"><img src="https://agentmods.dev/badge/skills/fmind/dot/github-pull-request.svg" alt="Measured on agentmods" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 685 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.

ModelPer sessionOnce invoked
Fable 5 $0.00039 $0.00685
Opus 5 $0.00019 $0.00342
Sonnet 5 $0.00008 $0.00137
Haiku 4.5 $0.00004 $0.00068

Measured yesterday against content hash 3b69db462143, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-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 yesterday.

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/github-pull-request/SKILL.md · 67 lines

How it starts

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

GitHub Pull Request

Create or update the pull request for the current branch against main with a What, Why, How, and Test plan body; feature-branch owns branch creation and conventional-commit the commits on it.

Workflow

  1. Stop on main: a PR must come from a feature branch.

  2. Gather context so the PR reflects the actual work, not only the commit subjects:

    git fetch origin main                                   # refresh origin/main for the ranges below
    git branch --show-current                               # current branch
    git status --short                                      # working tree state
    gh pr view --json number,state,url                      # existing PR for this branch (non-zero exit when none)
    git log --reverse --oneline origin/main..HEAD           # commits since main
    git diff --stat --find-renames origin/main...HEAD       # diff stats
    git diff --name-only --find-renames origin/main...HEAD  # changed files
    
  3. Write the title in imperative mood, under 72 characters.

  4. Write the body into a temporary file (never inline shell quoting) with these sections:

    ## What
    
    ## Why
    
    ## How
    
    ## Test plan
    
  5. Push the branch with an upstream when it has none: git push -u origin "$(git branch --show-current)".

  6. Create or update depending on step 2:

    gh pr edit --base main --title "<title>" --body-file <tmpfile>     # a PR exists
    gh pr create --base main --title "<title>" --body-file <tmpfile>   # no PR yet
    
  7. Report the PR URL, the final title, and the final body; if origin/main or GitHub auth is unavailable, explain the blocker and stop.

Official Skills

Upstream: cli/cli. List the current release, then install what the task needs at project scope after reviewing the snapshot (see agent-skills):

gh skill preview cli/cli gh
gh skill install cli/cli gh

Read the full file on GitHub · 67 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.

  1. yesterday First seen · 67 lines · 39 tokens per session scan A 3b69db462143

Subscribe to this mod's changes

github-pull-request is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 685 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-09-03.