A pull-request creation workflow for GitHub. A pull request is a proposed set of code changes for review before merging into a shared branch.

It helps open PRs, create Conventional Commits-style titles, summarize branch changes, use the repository PR template, and assign the project when GitHub access allows it.

It turns an already committed and pushed branch into a PR with a title and description that follow the repository’s rules.

How petermefrandsen/rtk-inspector configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to petermefrandsen/rtk-inspector. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/petermefrandsen/rtk-inspector/main/.github/skills/create-pr/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/petermefrandsen/rtk-inspector

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/petermefrandsen/rtk-inspector/create-pr/github.svg)](https://agentmods.dev/skills/petermefrandsen/rtk-inspector/create-pr)

Your own site

<a href="https://agentmods.dev/skills/petermefrandsen/rtk-inspector/create-pr"><img src="https://agentmods.dev/badge/skills/petermefrandsen/rtk-inspector/create-pr/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/petermefrandsen/rtk-inspector/create-pr"><img src="https://agentmods.dev/badge/skills/petermefrandsen/rtk-inspector/create-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,058 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.00044	$0.02058
Opus 5.5	$0.00018	$0.00823
Sonnet 5.5	$0.00009	$0.00412
Haiku 4.5	$0.00004	$0.00206

Measured 2mo ago against content hash b943e5371389, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-pr 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.

.github/skills/create-pr/SKILL.md · 203 lines

How it starts

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

create-pr

Mission

Create a GitHub pull request for the current branch with a valid Conventional Commits title and an auto-generated description that summarizes the actual changes.

Prerequisites

git and gh CLI installed and authenticated (gh auth status).
The gh token must include the project scope for project assignment. If missing, run: gh auth refresh -s project
The current branch is not main.
Changes have been committed and pushed to the remote.

PR title rules

The title must pass the repository PR title checker. The authoritative pattern is defined in .github/pr-title-checker-config.json — read that file at runtime to get the current CHECKS.regexp value rather than relying on a hardcoded pattern.

Additional prose rules (not fully enforced by the checker):

The ! breaking-change indicator must appear after the optional scope and before the :, never between the type and the scope (for example feat!(scope): is invalid; feat(scope)!: is correct).
The : must be followed by a single space and a non-empty description.

Allowed types: feat, fix, docs, test, ci, chore, refactor.

Format:

<type>[optional scope][!]: <description>

Examples:

feat(cmdb): add bulk object creation endpoint
fix(auth): handle expired JWT gracefully
docs: update README with new env vars
refactor(services)!: replace requests with httpx

PR description template

The body must use the structure from .github/pull_request_template.md:

# Pull request description

## Describe your changes

<auto-generated summary — see below>

## Issue ticket number and link

<leave blank or fill if the user provides one>

## Checklist before requesting a review

- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] Any dependent changes have been merged and published in downstream modules
- [ ] New or updated tests follow the AAA pattern and `test_<feature>_should_<expected behavior>_when_<state under test>` naming convention

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

2mo ago First seen · 203 lines · 44 tokens per session scan A b943e5371389

Subscribe to this mod's changes

create-pr is a skill published in the GitHub repository petermefrandsen/rtk-inspector (1 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 2,058 once invoked, about $0.0002 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.

Claude Code Git and workflow copilot gemini-cli rtk tokens

work-unit-commits

Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.

Gentleman-Programming/gentle-ai · 33 tokens

skill-design-lineage

Persist design documents with branch tracking, revision chains, and cross-session discovery.

nyldn/claude-octopus · 19 tokens

spec-kitty-git-workflow

Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…

Priivacy-ai/spec-kitty · 125 tokens

release

Release a new version of the DevoxxGenie IntelliJ plugin — prompt for the target version, bump it in the build files, write a curated CHANGELOG.md entry and plugin.xml change-notes from the git/PR history since the last tag, build to verify, then commit, tag, and publish a matching GitHub release. Use this whenever…

devoxx/DevoxxGenieIDEAPlugin · 121 tokens

github-review-pr

Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…

feiskyer/claude-code-settings · 90 tokens

git-commit

Git commit message generator that creates conventional commit messages based on code changes.

JackyST0/awesome-agent-skills · 18 tokens

rtk-inspector: Skill for Claude Code