@xuhaojun/githunk-darwin-arm64 0.3.2 → 0.3.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/githunk +0 -0
- package/package.json +2 -1
- package/skills/githunk-handoff/SKILL.md +53 -0
package/bin/githunk
CHANGED
|
Binary file
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@xuhaojun/githunk-darwin-arm64",
|
|
3
|
-
"version": "0.3.
|
|
3
|
+
"version": "0.3.4",
|
|
4
4
|
"description": "A review-first Git TUI combining lazygit's everyday Git workflow with focused hunk review. (darwin arm64 binary)",
|
|
5
5
|
"os": [
|
|
6
6
|
"darwin"
|
|
@@ -13,6 +13,7 @@
|
|
|
13
13
|
},
|
|
14
14
|
"files": [
|
|
15
15
|
"bin",
|
|
16
|
+
"skills/githunk-handoff",
|
|
16
17
|
"LICENSE"
|
|
17
18
|
],
|
|
18
19
|
"repository": {
|
|
@@ -0,0 +1,53 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: githunk-handoff
|
|
3
|
+
description: Use when a human reviewer asks an agent to handle githunk open objections, review handoff feedback, or respond to disputed Branch Review comments.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Githunk Handoff
|
|
7
|
+
|
|
8
|
+
## Overview
|
|
9
|
+
|
|
10
|
+
Treat the handoff as the human reviewer's durable work queue. Change code or record a disagreement; never decide that an objection is resolved.
|
|
11
|
+
|
|
12
|
+
## Workflow
|
|
13
|
+
|
|
14
|
+
1. From the repository being reviewed, read the canonical mailbox through the CLI:
|
|
15
|
+
|
|
16
|
+
```bash
|
|
17
|
+
githunk handoff --json
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
2. For every item, use its `path`, `side`, `startLine`, and `endLine` to inspect the current code and relevant diff. `replacement` is a proposed edit: apply it only when it remains correct in context.
|
|
21
|
+
3. Implement every objection you accept. Follow the repository's normal implementation and verification rules.
|
|
22
|
+
4. If you disagree or intentionally leave an item unchanged, persist the reason with its exact `id`:
|
|
23
|
+
|
|
24
|
+
```bash
|
|
25
|
+
githunk handoff reply --id <id> --body "why this change should not be made"
|
|
26
|
+
```
|
|
27
|
+
|
|
28
|
+
5. Report each item as **changed** or **replied**, plus verification evidence. Never report an item as resolved or addressed; the reviewer decides after inspecting the next revision.
|
|
29
|
+
6. Commit only when the user or repository workflow calls for a commit. The ledger remains `WAITING` until `HEAD` advances; after that, the reviewer reopens Branch Review to inspect the result.
|
|
30
|
+
|
|
31
|
+
## Quick reference
|
|
32
|
+
|
|
33
|
+
| Need | Command or action |
|
|
34
|
+
|---|---|
|
|
35
|
+
| Structured objections | `githunk handoff --json` |
|
|
36
|
+
| Human-readable objections | `githunk handoff` |
|
|
37
|
+
| Disagree or intentionally skip | `githunk handoff reply --id <id> --body <reason>` |
|
|
38
|
+
| Accept an objection | Edit and verify the code; write no reply |
|
|
39
|
+
| Resolve an objection | Do not do this; only the reviewer can resolve it |
|
|
40
|
+
|
|
41
|
+
`UNTOUCHED` means the anchored lines stayed byte-identical after `HEAD` advanced. `DISPUTED` means those lines stayed unchanged and the agent replied. Neither is an agent-controlled status.
|
|
42
|
+
|
|
43
|
+
## No handoff exists
|
|
44
|
+
|
|
45
|
+
If the CLI reports no handoff, ask the user to open githunk, press `b` for Branch Review, add objections with `c`, and press `A` to hand them off. githunk does not need to remain running while the agent works; the mailbox lives under Git metadata.
|
|
46
|
+
|
|
47
|
+
## Common mistakes
|
|
48
|
+
|
|
49
|
+
- Do not read or edit `.git/githunk/handoff/*.json` directly; use the CLI.
|
|
50
|
+
- Do not write status, resolution, or a synthetic completion record.
|
|
51
|
+
- Do not reply to accepted items merely to say they were changed; replies are for disagreements or intentional non-changes.
|
|
52
|
+
- Do not silently skip an unsafe or obsolete suggestion; reply with the reason.
|
|
53
|
+
- Do not assume a suggested replacement is correct without inspecting surrounding code.
|