菜单
List the work that's ready to pick up by scanning the project board for issues with Status "ready-for-work" and presenting a summarized, ranked shortlist. Use when the user asks "what's next", "what's up next", or invokes /up-next. Can hand a chosen issue to /pickup.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Address review comments left in a live hunk diff session, then commit the fixes locally. Use when the user says to check/address/handle their hunk comments (e.g. /hunk-comments, "address my hunk comments", "I left comments in hunk").
Compact the current conversation into a handoff document for a fresh agent to pick up. Use when the user asks to hand off, wrap up a session, or invokes /handoff.
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, mentions "grill me", or whenever a decision needs the user's input (always use this instead of AskUserQuestion).
Create atomic git commits from outstanding changes with terse, imperative messages. Pass --push to also push to the remote. Use when the user asks to commit (e.g. /commit, "commit this") or commit and push (e.g. /commit --push, "push this", "commit and push").
Pick up a GitHub issue and prepare to work it — read the issue thoroughly, research the codebase, grill the user on every open question until the plan is nailed down, then begin implementing. Use when the user wants to start work on an issue, invokes /pickup, or hands one over from /up-next.
Open a GitHub pull request for the current branch with a concise, template-conformant, PM-readable description. Links the related GitHub issue so it closes on merge and moves it to in-review. Use when the user asks to open or create a PR (e.g. /pr, "open a PR", "create a pull request"). Pass --draft for a draft PR.
| name | up-next |
| description | List the work that's ready to pick up by scanning the project board for issues with Status "ready-for-work" and presenting a summarized, ranked shortlist. Use when the user asks "what's next", "what's up next", or invokes /up-next. Can hand a chosen issue to /pickup. |
| disable-model-invocation | true |
| argument-hint | [owner/repo — defaults to current repo] |
| allowed-tools | ["Bash","Agent","Read"] |
Surface the issues that are ready to be worked on right now and present them as a tight shortlist the user can pick from.
Default to the current repo (cwd). If the user passed an owner/repo, target that instead.
ready-for-work is a Status field on the org's GitHub Project (v2), not an issue label — so gh issue list --label won't see it. Query the project board instead.
Requires the read:project scope. If a query fails with a missing-scope error, tell the user to run gh auth refresh -s read:project,project (interactive browser flow) and stop until they confirm.
Find the project, then list its items filtered to Status == ready-for-work:
# Resolve the org and project number (one project here: "Zodiac Rewrite Prototype" = #2 under galileo-inc)
OWNER=galileo-inc
PROJECT=$(gh project list --owner "$OWNER" --format json | jq -r '.projects[0].number')
# Items in ready-for-work — includes the board Size field when set
gh project item-list "$PROJECT" --owner "$OWNER" --format json --limit 100 \
| jq -r '.items[] | select(.status=="ready-for-work")
| {number: .content.number, title: .content.title, url: .content.url,
assignees: .content.assignees, size: .size, repo: .content.repository}'
If the list is empty, say so plainly and stop — don't pad with unrelated issues.
gh pr list --search "<issue#>" check), unless the user asked to include them.Size field when present; otherwise infer rough effort.work-finder agent rather than reading every thread inline. Tell it to restrict to the ready-for-work items found above (pass it the issue numbers). Use its output to order the list.Numbered list, terse. Per item:
Keep it scannable. No raw issue dumps.
End by offering to feed a chosen issue into /pickup (the ingestion + planning skill). If the user names a number, invoke /pickup <issue#>.