Menu
Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Configure the Obsidian task project mapping for the current repository — links a git repo to a parent note and task prefix in the vault. Use when the user says "set project", "configure project", "link this repo to tasks", or wants to set up Obsidian task tracking for a new repo. Config at ~/.obsidian-tasks/.
Update the status of an Obsidian vault task. Use when the user asks to update, change, or set the status of a task like PKB-0003 or D-0017, or says "mark as In Progress", "set to Done", etc. Config at ~/.obsidian-tasks/.
Add a comment or note to an existing Obsidian vault task. Use when the user asks to add a note, comment, update, or log progress on a task like PKB-0003. Config at ~/.obsidian-tasks/.
Create a new task in the Obsidian vault. Use when the user asks to create a task, add a task, or log new work to track. Drafts first and waits for approval before writing any files. Config at ~/.obsidian-tasks/.
Fetch and start an Obsidian vault task. Use when the user inputs a bare task code (e.g. PKB-0003, D-0017) or says "start task PKB-0003", "work on PKB-0003", "fetch PKB-0003", or similar. Reads the task file and full parent note, marks the task In Progress, then executes Mode 1 (Explore → Plan → Critique → Propose).
Keep a PR merge-ready by triaging comments, resolving clear conflicts, and fixing CI in a loop.
| name | split-to-prs |
| description | Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR. |
Turn one pile of work into a few small PRs.
reset --hard, clean -fdx, branch deletion, force-push, history rewrite) without explicit approval.main, so do not assume there is already a safe branch.git add . / git add -A.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.
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.
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.
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.