菜单
Inspect and control live Hunk diff-review sessions through the non-interactive `hunk session` CLI. Use when the user has Hunk running, wants an interactive diff walkthrough, or wants inline Hunk comments. The daemon uses localhost, so sandboxed agents must request network or sandbox access before discovering sessions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Restate the immediately preceding assistant response in plain, concise human language without jargon while preserving important details and useful formatting. Use when the user says "bro", asks for a simpler explanation, or wants a technical answer made easier to read.
Independently review a candidate software change against its original plan, repository constraints, behavior, tests, design quality, compatibility, security, operations, and verification evidence without modifying files. Use for review-only requests, fresh-context $ship review handoffs, or evidence-led diff assessment. Do not use to implement fixes, refactor code, resolve existing GitHub review threads, perform product or architecture design, or approve a change whose governing plan is missing.
Deploy one release-ready immutable software candidate through the repository's established deployment path, observe declared health signals, and stop, roll back, or hand off forward repair when rollout conditions fail. Use only when the user explicitly invokes $deploy with a target environment and deployment authority. Do not use for implementation, release-readiness review, CI-only verification, implicit production mutation, or a candidate lacking identity, recovery, and health evidence.
Resolve system boundaries, contracts, data and control flow, quality scenarios, failure behavior, and architectural tradeoffs for an active Neo task. Use only with an architecture-stage handoff generated by $neo. Do not use directly, reduce architecture to technology selection, or implement code.
Resolve system boundaries, contracts, data and control flow, quality scenarios, failure behavior, and architectural tradeoffs for an active Neo task. Use only with an architecture-stage handoff generated by $neo. Do not use directly, reduce architecture to technology selection, or implement code.
Convert approved Neo context and design into thin vertical implementation slices with focused verifiers, compatibility, rollout, rollback, and replan conditions. Use only with a delivery-stage handoff generated by $neo. Do not use directly, create horizontal layer batches, or implement the slices.
| name | hunk-review |
| description | Inspect and control live Hunk diff-review sessions through the non-interactive `hunk session` CLI. Use when the user has Hunk running, wants an interactive diff walkthrough, or wants inline Hunk comments. The daemon uses localhost, so sandboxed agents must request network or sandbox access before discovering sessions. |
Use only hunk session ... commands. The TUI belongs to the user; never launch
interactive hunk diff or hunk show commands yourself.
Use a balanced model at low effort for discovery, navigation, and structured session inspection; use medium effort when reviewing patches or drafting comments. Escalate to a frontier model at high effort only for security, data-loss, concurrency, release-critical, or nonlocal review risk. Treat the session state and focused diff as the verifier.
Hunk's daemon uses localhost. From a sandboxed harness, run discovery outside
the sandbox on the first attempt and request reusable approval for the
hunk session prefix when supported:
hunk session list --json
Repo; ask when several sessions fit.hunk session get <id> --json
hunk session review <id> --json
get to confirm the repository, window path, and loaded source.review --json before adding --include-patch for code that needs
inspection. Use context <id> --json only when current focus matters.hunk session navigate <id> --file src/App.tsx --hunk 2
hunk session reload <id> -- diff
hunk session comment add <id> --file README.md --new-line 103 \
--summary "Tighten this wording" --rationale "Explain why" --focus
hunk session comment apply <id> --stdin
--hunk, --old-line, or --new-line;
hunk and line numbers are 1-based.comment add for one focused note and comment apply with JSON on stdin
for a prepared batch.-- before the nested diff or show command in reload.hunk session --help for uncommon operations instead of guessing flags.