9 kensaurus

split-to-prs Skill

把当前工作拆分成小的、便于评审的 PR。当用户要求拆分某次对话、分支或变更集时使用。把整个脏工作区整理为一个可合并的 PR → workflow-release-prep。

安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。

查看源码

技能指令原文(SKILL.md)

Split to PRs

Turn one pile of work into a few small PRs.

Hard rules

  • Do not create branches, commit, push, or open PRs until the user approves the split plan.
  • Never discard user work. No destructive git commands (reset --hard, clean -fdx, branch deletion, force-push, history rewrite) without explicit approval.
  • Always save a recoverable snapshot before moving work around. This often starts from dirty work on main, so do not assume there is already a safe branch.
  • Stage only named files or hunks. No git add . / git add -A.

1. Check the state

Compare the current work to the repo's default branch, including committed and uncommitted changes. Summarize the real slices you see, and use the chat history to recover intent.

2. Propose the split

Use judgment on detail. Usually PR titles are enough. Add a one-line scope note only when a title is unclear. Show a Mermaid diagram when there are multiple slices.

Default to independent PRs off the default branch. Stack PRs only when the dependency is real.

Ask for approval before starting.

3. Execute the split

  • If there is uncommitted work, save a recoverable snapshot without changing the working tree:
  SHA=$(git stash create "pre-split")
  if [ -n "$SHA" ]; then
    git update-ref "refs/backup/pre-split-$(date +%s)" "$SHA"
  fi
  • For each approved slice, create a branch from the right base, stage and commit only the planned files or hunks, then push and open the PR.

4. Report back

Keep it short: PR titles and URLs, plus anything left on the starting branch or working tree. Do not delete the backup ref or original branch unless the user asks.