split-commit
Split an existing commit or PR into smaller reviewable pieces through a one-hunk patch queue.
Skill by szokeasaurusrex
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/szokeasaurusrex-split-commit
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
- Runs as
- Shell scripts
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/split-commit
What's inside
- Skill name
split-commit- Description
- Split an existing commit or PR into smaller reviewable pieces through a one-hunk patch queue. Use when extracting part of a commit, splitting a commit into multiple commits, or splitting PR changes from one or more source commits without starting from direct source edits.
- License
- MIT
- Instructions
- 59 lines in SKILL.md · view on GitHub
Before installing
- Ships executable scripts
Files (4)
- SKILL.md
- next-patch.sh · scripts/
- process-patch.sh · scripts/
- setup-split-patches.sh · scripts/
SKILL.md (first lines)
# Split Commit Use this skill when the user asks to split an existing commit or PR into smaller pieces through an explicit patch queue. ## Requirements - Start with a clean worktree and index unless the user explicitly says otherwise. - Do not start by editing source files directly. Use the generated one-hunk patches as the extraction source of truth. - After setup, do not enumerate `todo/` or read patch files directly. Inspect patches only through `scripts/next-patch.sh`. - Process the queue strictly in order. Do not inspect later entries before the current patch leaves `todo/`. - Every patch must leave `todo/` through exactly one state: `applied/`, `skipped/`, `partially-applied/`, or `merge-conflicted/`. - For `partial`, keep the moved patch as the audit artifact, then reduce that patch to the in-scope subset only. Do not introduce edits that are not already present in the surfaced patch. - Validate the repo state before creating final commits. ## Scripts - `scripts/setup-split-patches.sh` - `scripts/next-patch.sh` - `scripts/process-patch.sh` ## Workflow 1. Create the queue from a source commit or revision range. 2. Run `scripts/next-patch.sh` to get the next patch path and full patch content. 3. Decide only for that surfaced patch: `apply`, `skip`, or `partial`. 4. Run `scripts/process-patch.sh` for that action. 5. If the action is `partial`, perform the scoped manual edit immediately and keep only the in-scope subset from that patch. 6. If a patch reaches `merge-conflicted/`, resolve the reported conflicts before continuing. 7. Repeat until `scripts/next-patch.sh` prints `All patches are processed.`. ## Example loop ```bash scripts/setup-split-patches.sh --source 4a95362 --repo /abs/path/to/repo scripts/next-patch.sh --workdir /tmp/split-commit.ABC123 scripts/process-patch.sh \ --workdir /tmp/split-commit.ABC123 \ --patch /tmp/split-commit.ABC123/todo/003-file.patch \ --action apply scripts/next-patch.sh --workdir /tmp/split-commit.ABC123 scripts/process-patch.sh \ --workdir /tmp/split-commit.ABC123 \ --patch /tmp/split-commit.ABC123/todo/004-file.patch \ --action partial # then reduce that surfaced patch to the in-scope subset only scripts/next-patch.sh --workdir /tmp/split-commit.ABC123 ``` ## Notes - `scripts/setup-split-patches.sh` supports `--source <commit-ish>` and also accepts explicit revision ranges. - `scripts/next-patch.sh` is the only queue inspection entry point and is also the completion check. - `scripts/process-patch.sh --action apply` tries normal apply first, then falls back to `git apply --3way`.
From szokeasaurusrex/pi-agent, MIT.
More from szokeasaurusrex/pi-agent
- 0.599score
commit
szokeasaurusrex
Use this skill when asked to create or amend a commit.
SkillAFreshness: A★ 2Claude Code +9 - 0.557score
value-challenge
szokeasaurusrex
Mandatory adversarial value gate for every nontrivial code, configuration, documentation, process, or product change.
SkillBFreshness: B★ 2Claude Code +9 - 0.511score
plan
szokeasaurusrex
Use this skill when asked to plan something, or plan and implement.
SkillCFreshness: C★ 2Claude Code +9 - 0.507score
delegation-plan
szokeasaurusrex
Write plans intended for a cheaper or less capable implementation model.
SkillCFreshness: C★ 2Claude Code +9 - 0.507score
cargo
szokeasaurusrex
Use when initializing Rust projects or modifying Cargo.toml, Cargo.lock, cargo config, or other cargo-related files.
SkillCFreshness: C★ 2Claude Code +9 - 0.482score
thinking-through
szokeasaurusrex
Use when the user asks for ideas, brainstorming, discussion, exploration, possibilities, pros and cons, tradeoffs, or to "think through" something.
SkillCFreshness: C★ 2Claude Code +9 - 0.447score
github-issues-draft
szokeasaurusrex
Use when asked to create or draft GitHub issues.
SkillDFreshness: D★ 2Claude Code +9 - 0.443score
technical-writing
szokeasaurusrex
Use when drafting or editing persisted technical writing artifacts such as commit messages, issue bodies, PR descriptions, documentation comments, or…
SkillDFreshness: D★ 2Claude Code +9 - 0.443score
github-bare-worktree-clone
szokeasaurusrex
Create a GitHub repo as repo/.bare with repo/<branch> worktrees and origin-tracking branches.
SkillDFreshness: D★ 2Claude Code +9 - 0.442score
sentry-docs
szokeasaurusrex
Use whenever fetching documentation from docs.sentry.io or develop.sentry.dev.
SkillDFreshness: D★ 2Claude Code +9 - 0.439score
context-fork
szokeasaurusrex
Checkpoint, inspect, and return through session tree branches.
SkillDFreshness: D★ 2Claude Code +9 - 0.438score
skill-writing
szokeasaurusrex
Use when creating or updating agent skills (`skills/<name>/SKILL.md` files).
SkillDFreshness: D★ 2Claude Code +9
Signals
- Stars
- 2
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Apr 15, 2026 (6 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/szokeasaurusrex/pi-agent
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
More from szokeasaurusrex
- 0.599score
commit
szokeasaurusrex
Use this skill when asked to create or amend a commit.
SkillAFreshness: A★ 2Claude Code +9 - 0.557score
value-challenge
szokeasaurusrex
Mandatory adversarial value gate for every nontrivial code, configuration, documentation, process, or product change.
SkillBFreshness: B★ 2Claude Code +9 - 0.511score
plan
szokeasaurusrex
Use this skill when asked to plan something, or plan and implement.
SkillCFreshness: C★ 2Claude Code +9 - 0.507score
cargo
szokeasaurusrex
Use when initializing Rust projects or modifying Cargo.toml, Cargo.lock, cargo config, or other cargo-related files.
SkillCFreshness: C★ 2Claude Code +9 - 0.507score
delegation-plan
szokeasaurusrex
Write plans intended for a cheaper or less capable implementation model.
SkillCFreshness: C★ 2Claude Code +9 - 0.482score
thinking-through
szokeasaurusrex
Use when the user asks for ideas, brainstorming, discussion, exploration, possibilities, pros and cons, tradeoffs, or to "think through" something.
SkillCFreshness: C★ 2Claude Code +9
Cite this page
split-commit skill. Agent Mart. https://agentmart.dev/skills/szokeasaurusrex-split-commit (last updated 2026-10-24)