A pull-request helper that checks the branch, helps you write a title, proofreads your description, and opens the request. A pull request is a request for others to review and merge your code changes.

Use it to inspect commits against a base branch, suggest a title, proofread your text, and open a pull request. It can also support an automatic mode when nobody will write or approve the description.

It handles the checks and GitHub steps around opening a pull request without writing the feature description in your voice. This keeps the final record of the change aligned with what you intended.

pr — Skill for Claude Code by thoughtbot/rails-consultant

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 thoughtbot/rails-consultant --skill pr

Clone the repo

git clone --depth 1 https://github.com/thoughtbot/rails-consultant

Made for: Claude Code.

Or install rails-consultant, the plugin that ships this one along with the rest of its 15 skills.

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/thoughtbot/rails-consultant/pr/github.svg)](https://agentmods.dev/skills/thoughtbot/rails-consultant/pr)

Your own site

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

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

When invoked 3,921 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.00022	$0.03921
Opus 5.5	$0.00009	$0.01568
Sonnet 5.5	$0.00004	$0.00784
Haiku 4.5	$0.00002	$0.00392

Measured today against content hash 40a13cc93615, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 today.

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/pr/SKILL.md · 348 lines

How it starts

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

PR

The LLM wrote the commits. The user owns the feature, so the user writes the description. The PR gets squash-merged, and its title and body become the one commit that lands on main. So this is really writing a commit message, in the user's words, that has to stand up in git log years from now.

Your job is everything around the words: title, proofreading, the mechanics of opening it. The failure to avoid is drafting the description yourself. Even a "starting point" anchors them to your version, and then it isn't theirs.

recon --> brief + title --> user writes --> proof --> sign-off --> open
                             ^                        |
                             +------ changes ---------+

Arguments start with --auto? Nobody will write or approve the description. Read Autonomous mode first; it replaces steps 2 through 6.

1. Recon

Base branch is $ARGUMENTS (minus --auto and --screenshots), or the repo default (gh repo view --json defaultBranchRef, falling back to main).

Read, don't ask:

git status. Uncommitted changes or sitting on the base branch: stop and say so. Committing and branching are other jobs.
git log <base>..HEAD and git diff <base>...HEAD --stat. What the branch does, so you can title it and later check their description against it.
House style: gh pr list --state merged --limit 15 --json title,body, plus git log <base> --oneline -20 for repos without gh history. Look at mood ("Add" vs "Added"), prefixes (feat:, [JIRA-123]), capitalization, how code names are marked (backticks?), length, and where bodies put issue links.
PR template: pull_request_template.md, any case, in .github/, the repo root, or docs/. A .github/PULL_REQUEST_TEMPLATE/ folder holds several; pick the one that fits the branch.
The issue the branch works on: a number or issue URL in the branch name (42-shipping-emails, issue-42), the commits, or a SPEC the branch adds or names. Only what those say; don't search the tracker for a match.

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

today First seen · 348 lines · 22 tokens per session scan A 40a13cc93615

Subscribe to this mod's changes

pr is a skill published in the GitHub repository thoughtbot/rails-consultant (29 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 3,921 once invoked, about $0.0001 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-11-07.

Git and workflow claude-code-consulting claude-code-plugin claude-code-rails claude-code-skill claude-code-skills claude-skills

pr next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
prthoughtbot/rails-consultant	Skill	29	yesterday	MIT	A	22	Claude Code
watch-proliver-kriska/claude-elixir-phoenix	Skill	573	yesterday	MIT	A	50	Claude Code
releaseoliver-kriska/claude-elixir-phoenix	Skill	573	yesterday	MIT	A	60	Claude Code
catchupoliver-kriska/claude-elixir-phoenix	Skill	573	yesterday	MIT	A	48	Claude Code
pr-reviewoliver-kriska/claude-elixir-phoenix	Skill	573	yesterday	MIT	A	59	Claude Code
phx-pr-reviewoliver-kriska/claude-elixir-phoenix	Skill	573	yesterday	MIT	A	61	Claude Code, Codex
craft-plugin-releasemichtio/craftcms-claude-skills	Skill	88	yesterday	MIT	A	72	Claude Code