菜单
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").
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | hunk-comments |
| description | 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"). |
| allowed-tools | ["Bash","Read","Edit","Write","Grep","Glob","Skill"] |
The user reviews a diff in a live hunk TUI session (usually launched via
review, which pins the diff to the merge base with the default branch
and watches for file changes). They leave inline comments; your job is to
address each one in code, clean up the comments, and commit.
The TUI belongs to the user - NEVER run hunk diff/hunk show yourself.
Interact only through hunk session * commands. For the full session command
reference, read the bundled skill at the path printed by hunk skill path.
hunk session list --json. If none, ask the user to
run review in the repo first, then stop. If multiple match, select
by --repo <repo-root> or explicit session id.hunk session comment list --repo . --type user --json.
If empty, also try without --type (older comment views). If still empty,
report that and stop.hunk session review --repo . --json (and
--include-patch only for files you truly need raw diff text for) to see
the hunk structure the comment anchors to.hunk session navigate --repo . --next-comment or --file/--new-line),
leave an agent note explaining the question
(hunk session comment add --repo . --file <f> --new-line <n> --summary "..." --author "claude"),
and ask the user before changing anything there.hunk session comment rm --repo . <comment-id>. If removal of a
user-authored note is refused, leave it and add an adjacent agent note
prefixed "addressed:" describing the fix.commit skill to commit the fixes locally. Never
push unless the user asks. If fixes are unrelated to each other, let the
commit skill split them into atomic commits as usual.hunk session list shows nothing
while hunk is visibly running, sandbox loopback blocking is the likely
cause; retry with escalated permissions.newLine = current
file, oldLine = base side). Verify against the actual file before
editing - the file may have shifted since the comment was left.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.
Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when the user wants to convert a plan into issues, create implementation tickets, or break work down into issues.