split-publishlisted
Install: claude install-skill suho-han/one-click-ai-tools
# Split Publish
## Overview
Use this skill when worktree changes are mixed and the user wants commits separated by job before publishing.
## Workflow
1. Inspect repository state first.
- Run `git status -sb`, `git diff --stat`, `git branch --show-current`, and `git remote -v`.
- If push may be required, run `git status --porcelain=v2 --branch`.
- If worktree is clean, stop and report there is nothing to publish.
2. Load repository guidance before grouping.
- Read root `AGENTS.md` if present.
- Read local docs for branch/release/validation policy when relevant.
3. Propose commit groups.
- Inspect diffs per file with `git diff -- <path>` when boundaries are unclear.
- Group by one coherent task per commit.
- For each group, provide:
- label
- exact file list
- commit message
- push/PR intent
- If grouping is ambiguous, ask the user.
4. Confirm scope before staging.
- On mixed worktree, get explicit confirmation before staging.
- Do not default to `git add -A`.
- Use explicit path staging: `git add -- <path>...`.
5. Commit and push group-by-group.
- Stage only approved files.
- Verify staged scope using `git diff --cached --stat` (and `git diff --cached` if needed).
- Commit with terse task-level message.
- Run minimal relevant validation before first push.
- Push each commit in order:
- if no upstream: `git push -u origin $(git branch --show-current)`
- else: `git push`
6. Open draft PR only when explicitly requested.
- Do not open PR automatically.
-