divide
Split a GitHub issue or task into session-sized issues and put them on the board. Use when a task is too big for one session or remaining work must be split off.
- License 许可
- MIT
- 所属仓库
- KrishP147/skills
- 最近更新
- 2026-11-10
- Stars
- ★ 37
- Forks
- 1
01 前言 Front Matter
- name
- divide
- description
- Split a GitHub issue or task into session-sized issues and put them on the board. Use when a task is too big for one session or remaining work must be split off.
- argument-hint
- issue number or task description
02 资源文件 1
- 参考文档README.md4.3 KB
03 SKILL.md 正文
- Target repo per BOARD.md: resolve
origin(this skill needs it on GitHub),-R <owner>/<repo>on everyghcall, and on a fork ask which repo to write to before any write. - Read the target (
gh issue view <n> -R <owner>/<repo>, or the user's description), its existing children (gh api repos/<owner>/<repo>/issues/<n>/sub_issues, whichissue viewdoesn't show, and any task list in the body), plus any detail the caller passes (fromwayfinder: decision rows and resolution comments). - Session-sized = fits the ~75K-token smart zone and ends in one PR. Target already fits one session → don't divide: say so and stop. Else propose 2+ session-sized pieces, each with a "done when", covering only what no existing child (open or closed) already covers; list those children in the proposal. Show the split; create nothing yet. You revise the split → show it again and wait for the yes.
- On yes:
gh issue create -R <owner>/<repo> --title "<piece>" --body "Part of #<n>. <details>"per piece, then add a task-list checkbox per child to the parent's body; a parent that already has sub-issues gets each child attached as one instead (gh api repos/<owner>/<repo>/issues/<n>/sub_issues -X POST -F sub_issue_id=<id>,<id>fromgh api repos/<owner>/<repo>/issues/<a> -q .id), no checkboxes. Target read from another repo than the one written to (fork, per BOARD.md) → full cross-refs:Part of <owner>/<repo>#<n>naming the target's repo, and edit the parent (checkboxes as<owner>/<repo>#a, or sub-issue attach) only after a yes naming the parent's repo, else skip them and say so; the roadmap line (step 5) names children the same way (#n → <owner>/<repo>#a). Free-text target (no issue number) → there is no parent: omit "Part of", the checkboxes and the roadmap link (steps 3 and 5), and put the shared context in each child's body. - Put each child on the board at Todo (BOARD.md).
- Roadmap doc links the parent → add
#n → #a, #bbeside it and commit only that file (git add <roadmap path>), asdocs: divide #n into #a/#b/#c…(every child). Commit on the current branch; on the default branch, make a branch first per the repo's branch rules, and once committed report the branch + SHA, ask whether to push and open a PR (push only on a yes), then switch back to the branch you started on. - Issue target: parent now only tracks children → say so; offer to close it once they land.
04 同仓库更多 Skills
wayfinder
Plan an effort too big for one session as a map of decision tickets (GitHub issue + sub-issues) and resolve them one per session until the way is clear, then hand off to divide.
skill
暂无简介
teammate-brief
Write an onboarding document for a person joining or picking up a project — what it is, setup steps verified by running them, env var names and where to get them, tasks with "done when", owners, don't-touch list. Use for "brief my teammate", "onboarding doc for X", "hand this project to someone".
switch
Move this conversation to another Claude account (the previous one, or one by name), or set up, add, remove, rename and list accounts.
spend-gate
Gate any billable action (GPU pods/instances, paid APIs or tiers, cloud credits) behind a cost estimate, a live balance check, and an explicit yes for that action. Use before any create/deploy on a paid provider (runpodctl, vultr-cli, aws/gcloud/az, modal, provider MCP create/deploy/run/start/update), any paid API call, or when spend-guard blocks one.
sitrep
Live status of this session in ≤10 lines — what's running, git state, PRs + CI, asked vs done, what needs the user, and a SAFE/NOT SAFE close verdict. Use for "how's it going", "status update", "what's running", "can I close this".