agentmods.dev

ralphctl: Skill for Claude Code

.claude/skills/merge-pr/SKILL.md

merge-pr is a skill for Claude Code from lukas-grigis/ralphctl. It costs 70 tokens per session (1,061 once invoked), scanned A, original, MIT.

A procedure for merging an open pull request, which is a proposed code change awaiting review, into the repository's main branch. It waits for automated checks and uses a merge commit with administrator bypass.

In plain words
What is it for?
Use it when asked to merge or ship a pull request. It identifies the relevant request, waits for CI checks, reports failures, and merges only an eligible request targeting the main branch.
Why use it?
It prevents unfinished or failing changes from being merged. It also handles this repository's requirement for merge commits and its review restriction.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is lukas-grigis/ralphctl's own configuration. It tells Claude Code how to work on ralphctl itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ralphctl configures →

not rated 23repo today A scan SkillSpector: pass 70 tokens original MIT
View source ↗ lukas-grigis/ralphctl npmjs.com
Reuse

Borrowing it

Nothing to install: this file belongs to lukas-grigis/ralphctl. 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/lukas-grigis/ralphctl/main/.claude/skills/merge-pr/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/lukas-grigis/ralphctl

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.

agentmods badge for merge-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/merge-pr/github.svg)](https://agentmods.dev/skills/lukas-grigis/ralphctl/merge-pr)
Your own site
<a href="https://agentmods.dev/skills/lukas-grigis/ralphctl/merge-pr"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/merge-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.

agentmods 80×15 button for merge-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/lukas-grigis/ralphctl/merge-pr"><img src="https://agentmods.dev/badge/skills/lukas-grigis/ralphctl/merge-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,061 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00070 $0.01061
Opus 5 $0.00035 $0.00531
Sonnet 5 $0.00014 $0.00212
Haiku 4.5 $0.00007 $0.00106

Measured 9d ago against content hash a8a53354ae46, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

merge-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 9d 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.

.claude/skills/merge-pr/SKILL.md · 89 lines

How it starts

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

Merge PR

Standard end-of-PR landing flow for lukas-grigis/ralphctl.

Repo + branch-protection facts that shape this flow (verified via gh repo view / gh api .../branches/main/protection):

  • Only merge commits allowed — squash and rebase are off. gh pr merge --squash would 422.
  • deleteBranchOnMerge: true — branches auto-delete after merge. Do not pass --delete-branch.
  • main requires 1 approving review. Solo maintainer can't self-approve, so admin bypass is the standard tool here. enforce_admins is false, so the bypass is honored by the API.

Args

  • <pr-number> (optional) — when omitted, derive from the current branch via gh pr view --json number,....

Flow

  1. Resolve the PR. If no number given:

    gh pr view --json number,title,state,headRefName,baseRefName,mergeable

    Bail if state != OPEN or baseRefName != main. Show the user title + headRefName so they see what they're about to land.

  2. Watch CI. Block until checks finish:

    gh pr checks <num> --watch --fail-fast

    On failure: surface the failing check name + URL. Do not retry, do not merge. Hand back to the user — they decide whether to push a fix or close the PR.

  3. Merge with admin bypass.

    gh pr merge <num> --merge --admin

    --admin is the load-bearing flag — it tells the GitHub API to use the caller's admin permissions to merge through the required-review rule.

  4. Confirm. Print the merge commit SHA:

    gh pr view <num> --json mergeCommit -q .mergeCommit.oid

  5. Clean up the trailing branch. The remote branch is gone (deleteBranchOnMerge: true handled it), but the local copy and stale remote-tracking ref still linger. Switch back to main and delete them:

    BRANCH="$(gh pr view <num> --json headRefName -q .headRefName)"
git checkout main
git pull --ff-only origin main           # fast-forward to the new merge commit
git fetch --prune                          # drop the stale `origin/<branch>` ref
git branch -D "$BRANCH" 2>/dev/null || true   # ok if it was never checked out locally

Read the full file on GitHub · 89 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. 9d ago First seen · 89 lines · 70 tokens per session scan A a8a53354ae46

Subscribe to this mod's changes

merge-pr is a skill published in the GitHub repository lukas-grigis/ralphctl (23 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 1,061 once invoked, about $0.0003 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-30.

Git and workflowReleasesaianthropicclaudeclicopilotdeveloper-tools
Related

Other skills, from other repositories

pypi-release

This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.

alchemiststudiosDOTai/tunacode · 52 tokens

release

Prepare a version release — bump version files, commit, and tag. Just run /release with no arguments.

RockyHong/super-bootstrap · 24 tokens

release-init

Detect project type and generate a tailored project-level /release skill. Run once per project to set up releasing.

RockyHong/super-bootstrap · 25 tokens

github

Full-featured GitHub integration via the gh CLI. Manage repositories, issues, pull requests, CI/CD workflows, releases, and make raw API calls.

aaronboshart1/orionomega · 0 tokens

opensource

Open-source pipeline: fork, sanitize, and package private projects for safe public release. Chains 3 agents (forker, sanitizer, packager). Triggers: '/opensource', 'open source this', 'make this public', 'prepare for open source'.

herakles-dev/opensource-pipeline · 54 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