Borrowing it
Nothing to install: this file belongs to causify-ai/helpers. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/causify-ai/helpers/master/.claude/skills/github.get_pr_ready_to_merge/SKILL.mdgit clone --depth 1 https://github.com/causify-ai/helpersWrote 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.
[](https://agentmods.dev/skills/causify-ai/helpers/github.get_pr_ready_to_merge)<a href="https://agentmods.dev/skills/causify-ai/helpers/github.get_pr_ready_to_merge"><img src="https://agentmods.dev/badge/skills/causify-ai/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.
<a href="https://agentmods.dev/skills/causify-ai/helpers/github.get_pr_ready_to_merge"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/github.get_pr_ready_to_merge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.01155 |
| Opus 5.5 | $0.00006 | $0.00462 |
| Sonnet 5.5 | $0.00003 | $0.00231 |
| Haiku 4.5 | $0.00001 | $0.00115 |
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 16d 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.
How it starts
The opening of the file, as written. The whole thing — 139 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, fixing anything that comes up, so the PR is ready to be reviewed and merged
Workflow
Create and Update a Plan
-
Create a file
plan-github.get_pr_ready_to_merge.mdwith a plan in the form of a bullet list of actions and maintain it updated, by marking each action- [.] when something is in progress
- when something is done
- [F] when something 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-based linter on the branch, asking it to leave
TODOs instead of silently rewriting the code> linters2/cc_lint.py --branch --add_todos -
Commit the added
TODOs together with any other pending changes, following "Never Commit Junk Files" below
Resolve the Added TODOs
- For each file that
cc_lint.pyannotated, use/coding.todoai_gpto implement theTODO(ai_gp)items it added - Commit the fixes, following "Never Commit Junk Files" below
Run the Standard Linter
-
Run the repo's standard linter on the branch
> linters2/lint.py --branch -
Commit any resulting changes, following "Never Commit Junk Files" below
Fix Pyright Issues
- Fix the pyright warnings and errors in the branch
> linters2/lint.py --clear_actions --action "pyright" --branch - Commit any resulting changes, following "Never Commit Junk Files" below
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.
- 16d ago Changed · -2 lines dfe3414b6f4d
- 29d ago First seen · 141 lines · 14 tokens per session scan A b07350a036bb
github.get_pr_ready_to_merge is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session and 1,155 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-09-18.
Other skills, from other repositories
model-merging
Merge multiple fine-tuned models using mergekit to combine capabilities without retraining. Use when creating specialized models by blending domain-specific expertise (math + coding + chat), improving performance beyond single models, or experimenting rapidly with model variants. Covers SLERP, TIES-Merging, DARE, Task…
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
cw-gates
Use before claiming any Codewhale change is done, green, or ready to land: the focused-to-broad verification ladder, the budget checks CI enforces, and the rules for what counts as a passing test.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
release-safety
Release safety rules. INVOKE WHEN: yarn release, npm publish, release canary, release packages, publishing, skip checks, skip tests. NEVER skip checks or tests without explicit permission.