rebase-pr

A pull-request workflow that rebases a branch onto its target branch, signs the resulting commits, and pushes directly to that target branch.

In plain words
What is it for?
Use it to rebase and merge pull requests in repositories that allow direct pushes to the target branch.
Why use it?
It handles cases where the standard GitHub rebase merge cannot create signed commits, while stopping workflows that would violate a repository's branch rules.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/dryvist/claude-code-plugins/rebase-pr
Any agent
npx skills add dryvist/claude-code-plugins --skill rebase-pr
Clone the repo
git clone --depth 1 https://github.com/dryvist/claude-code-plugins

Made for: Claude Code, Codex.

Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,349 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00052 $0.02349
Opus 5 $0.00026 $0.01175
Sonnet 5 $0.00010 $0.00470
Haiku 4.5 $0.00005 $0.00235

Measured 2d ago against content hash 4b583675b5ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rebase-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 2d 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-workflows/skills/rebase-pr/SKILL.md · 245 lines

How it starts

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

rebase-pr

Merge a PR using local git rebase + signed commits + a direct push to the PR's base branch.

gh pr merge --rebase cannot sign commits. Local rebase with commit.gpgsign=true signs every rebased commit. Pushing the base branch directly auto-closes the PR.

This only works where direct pushes to the base branch are allowed: trunk repos' main, or a git-flow repo's develop. Git-flow's main accepts merge commits only and never direct pushes — Step 0 refuses before any of this runs.

Dispatch

MANDATORY FIRST STEP: Spawn a Haiku subagent using the Agent tool with mode: "bypassPermissions". Pass all content starting from Prerequisite: Validate Base Branch through end-of-document as the agent prompt; include the current branch name and PR number. Do not execute any steps yourself — the subagent runs the complete workflow autonomously with all permissions auto-accepted.

If the Haiku subagent cannot be spawned, becomes unavailable, or encounters an unrecoverable error while running this workflow, clearly report the failure to the user and ask whether to (a) retry spawning the subagent or (b) proceed manually by following the remaining steps of this document together step-by-step.

Prerequisite: Validate Base Branch

Resolve the PR's base branch and the repo's default branch. Replace <PR_NUMBER> before running:

BASE_BRANCH=$(gh pr view <PR_NUMBER> --json baseRefName --jq '.baseRefName')
DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name')

If BASE_BRANCH == main AND DEFAULT_BRANCH == develop (repo is on git-flow — see /gh-cli-patterns Canonical Default-Branch Detection), ABORT:

"This is a developmain promotion PR on a git-flow repo. Direct pushes to main are banned there — main accepts merge commits only, with no exceptions. Run /promote-release instead."

Read the full file on GitHub · 245 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. 2d ago First seen · 245 lines · 52 tokens per session scan A 4b583675b5ee

Subscribe to this mod's changes

rebase-pr is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 52 tokens to every session and 2,349 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-31.

Related

Other skills, from other repositories

draper-decorators

This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…

hoblin/claude-ruby-marketplace · 131 tokens

rspec

This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…

hoblin/claude-ruby-marketplace · 125 tokens

activerecord

This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…

hoblin/claude-ruby-marketplace · 180 tokens

dragonruby

This skill should be used when the user asks to "create a game", "make a game", "game development", "dragonruby", "drgtk", "game loop", "tick method", "sprite rendering", "game state", or mentions args.outputs, args.state, args.inputs, coordinate system, collision detection, animation frames, or scene management.…

hoblin/claude-ruby-marketplace · 100 tokens

mcp-server

This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when…

hoblin/claude-ruby-marketplace · 98 tokens

ratatui-ruby

This skill should be used when the user asks to "create a TUI", "terminal interface", "terminal UI", "ratatui", "ratatui-ruby", "inline viewport", "full-screen terminal app", "terminal widgets", "tui.draw", "tui.pollevent", or mentions RatatuiRuby.run, managed loop, terminal rendering, Tea MVU, or building CLI…

hoblin/claude-ruby-marketplace · 119 tokens