github-pull-request

A GitHub pull-request workflow for proposing changes from one branch for review before they are merged. It creates or updates a structured description covering what changed, why, how, and testing.

In plain words
What is it for?
Use it to open or update a pull request for the current feature branch, including pushing that branch when needed.
Why use it?
It removes the need to gather branch details and write the pull-request description manually.

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

Made for: Claude Code, Codex.

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 610 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.00038 $0.00610
Opus 5 $0.00019 $0.00305
Sonnet 5 $0.00008 $0.00122
Haiku 4.5 $0.00004 $0.00061

Measured yesterday against content hash f64bfc81dc6e, 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 · 72 lines

How it starts

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

Create GitHub Pull Request

Create or update a GitHub pull request for the current branch against main.

Context Gathering

Gather context before drafting:

  • git fetch origin main — refresh origin/main so the ranges below are accurate.
  • git config --get remote.origin.url — origin URL.
  • git branch --show-current — current branch.
  • git status --short — working tree state.
  • gh pr view --json number,state,url — detect an existing PR for this branch (exits non-zero / empty when none, keying the create-vs-edit choice).
  • 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.

Workflow

  1. If the current branch is main, stop and say a PR must come from a feature branch.

  2. Inspect changed files as needed so the PR matches the actual work, not just the commit subjects.

  3. Write a clear PR title in imperative mood, under 72 characters.

  4. Write a Markdown body with these sections:

    ## What
    
    ## Why
    
    ## How
    
    ## Test plan
    
  5. Push the current branch to origin with upstream if needed (git push -u origin <branch>).

  6. If a PR already exists for this branch, update it:

    gh pr edit --base main --title "<title>" --body-file <tmpfile>
    
  7. Otherwise create it:

    gh pr create --base main --title "<title>" --body-file <tmpfile>
    
  8. Use a temporary file for the PR body instead of inline shell quoting.

  9. After success, print the PR URL, the final title, and the final body.

  10. If origin/main or GitHub auth is unavailable, explain the blocker briefly and stop.

Gotchas

  • Keep the final response compact.
  • Never force-push to main.

Documentation

Read the full file on GitHub · 72 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 · 72 lines · 38 tokens per session scan A f64bfc81dc6e

Subscribe to this mod's changes

github-pull-request is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 610 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-31.

Related

Other skills, from other repositories

dotfiles-bootstrap

Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.

sebastienrousseau/dotfiles · 88 tokens

vibe

Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…

sebastienrousseau/dotfiles · 137 tokens

aiq-research

Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.

laurigates/dotfiles · 25 tokens

obsidian-bases

Obsidian Bases database feature for YAML-based interactive note views. Use when creating .base files, writing filter queries, building formulas, configuring table/card views, or working with Obsidian properties and frontmatter databases.

laurigates/dotfiles · 49 tokens

telegram

Send notifications, interactive questions, or multiple-choice polls to the user via Telegram. Use when the user asks to be notified ("ping me", "notify me on Telegram", "ask me when..."), when a long-running task finishes and the user is likely away, when an irreversible action needs out-of-band confirmation, or when…

laurigates/dotfiles · 117 tokens

chezmoi-expert

Comprehensive chezmoi dotfiles management expertise including templates, cross-platform configuration, file naming conventions, and troubleshooting. Covers source directory management, reproducible environment setup, and chezmoi templating with Go templates. Use when user mentions chezmoi, dotfiles, cross-platform…

laurigates/dotfiles · 88 tokens