What is github.get_pr_ready_to_merge?

A workflow for preparing a GitHub pull request (PR), a proposed code change, for review and merging. It runs code checks, local tests, and GitHub's automated checks, then fixes reported problems.

Use it to inspect the current PR, run AI and standard linters, run local tests, monitor GitHub CI, and report or fix failures.

It gathers the checks needed before review in one process, so failures are found and addressed before the PR is merged.

github.get_pr_ready_to_merge — Skill for Claude Code by gpsaggese

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 gpsaggese/helpers --skill github.get_pr_ready_to_merge

Clone the repo

git clone --depth 1 https://github.com/gpsaggese/helpers

Made for: Claude Code.

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/gpsaggese/helpers/github.get_pr_ready_to_merge/github.svg)](https://agentmods.dev/skills/gpsaggese/helpers/github.get_pr_ready_to_merge)

Your own site

<a href="https://agentmods.dev/skills/gpsaggese/helpers/github.get_pr_ready_to_merge"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/github.get_pr_ready_to_merge/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/gpsaggese/helpers/github.get_pr_ready_to_merge"><img src="https://agentmods.dev/badge/skills/gpsaggese/helpers/github.get_pr_ready_to_merge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,042 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.00014	$0.01042
Opus 5.5	$0.00006	$0.00417
Sonnet 5.5	$0.00003	$0.00208
Haiku 4.5	$0.00001	$0.00104

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

Security

Grade A, and why

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

.claude/skills/github.get_pr_ready_to_merge/SKILL.md · 127 lines

How it starts

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

Goal

Run the AI lint, the standard linter, the local tests, and GitHub CI for the current PR, and fix anything that comes up, so the PR is ready to review and merge

Workflow

Create and Update a Plan

Create plan-github.get_pr_ready_to_merge.md, a bullet list of actions. Keep it updated: [.] in progress, [x] done, [F] failed

E.g.,

# Plan: get PR #... ready to merge

- [ ] Get PR number and branch name
- [ ] Make sure PR is ready (not draft)
- [ ] Run AI lint with --add_todos, commit TODOs
- [ ] Resolve added TODO(ai_gp) items
- [ ] Run standard linter, fix issues
- [ ] Make Sure The Affected Local Tests Pass
- [ ] Make local tests pass
- [ ] Run and monitor GitHub CI
- [ ] Report status on PR
- [ ] Fix any CI failures

Get the PR Number and Branch Name

Get the PR number:

> GH_PR_NUM=$(gh pr view --json number -q .number)

Get the branch name:

> BRANCH_NAME=$(git branch --show-current)

Run the AI Lint and Add TODOs

Run the AI linter on the branch. Make it leave TODOs, not silently rewrite code:
```
> linters2/cc_lint.py --branch --add_todos
```
Commit the added TODOs with pending changes (see "Never Commit Junk Files")

Resolve the Added TODOs

For each file that cc_lint.py annotated, use /coding.todoai_gp to implement its TODO(ai_gp) items
Commit the fixes (see "Never Commit Junk Files")

Run the Standard Linter

Run the standard linter on the branch:
```
> linters2/lint.py --branch
```
Commit any resulting changes (see "Never Commit Junk Files")

Fix Pyright Issues

Fix the pyright warnings and errors in the branch

> linters2/lint.py --clear_actions --action "pyright" --branch

Commit any resulting changes (see "Never Commit Junk Files")

Make Sure The Affected Local Tests Pass

Run the tests affected by the change, using
```
> pytest <TEST_NAMES>
```
to iterate, then check all builds with pytest_multi_build.py
```
> pytest_multi_build.py --target <TEST_NAMES>
```

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

yesterday First seen · 127 lines · 14 tokens per session scan A 6f042a1de4a0

Subscribe to this mod's changes

github.get_pr_ready_to_merge is a skill published in the GitHub repository gpsaggese/helpers (158 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 1,042 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-06.

Commits Git and workflow Testing

github.get_pr_ready_to_merge next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
github.get_pr_ready_to_mergegpsaggese/helpers	Skill	158	today	Apache-2.0	A	14	Claude Code
create-prprisma/orm	Skill	48k	today	Apache-2.0	A	48	Claude Code, Codex
git-commitThinkInAIXYZ/deepchat	Skill	6.4k	yesterday	Apache-2.0	A	15	Claude Code, Codex
repo-syncdavidondrej/skills	Skill	4.3k	yesterday	MIT	A	25	Claude Code, Codex
engineer-bot-opsmakecindy/cindy	Skill	9.4k	today	Apache-2.0	A	57	Claude Code, Codex
mcore-split-prNVIDIA/skills	Skill	3.9k	today	Apache-2.0	A	25	Claude Code
git-commit-writermergisi/awesome-openclaw-agents	Skill	4.1k	3d ago	MIT	A	53	Claude Code, Codex