opening-hunk
Skill4 starsChanged 21 days agoMITView on GitHub
Prints the command that opens hunk, the terminal diff viewer, on the current directory or worktree, for a local session or an SSH one (also inside herdr panes). Use whenever the user wants to see or review a diff, a worktree or a staged change in the terminal, asks for hunk, or wants a review alternative to an IDE on a remote machine, even if they do not name this skill. The agent never runs hunk: it is a TUI the user opens in a new terminal. For the full IDE use opening-zed instead.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .copilot/copilot-instructions.mdCopilot instructions
- acting-as-diegoferigoSkill
- creating-skillsSkill
- gh-stackSkill
- guide-me-throughSkill
- opening-zedSkill
- orchestrating-agentsSkill
- using-worktrunkSkill
- working-in-zedSkill
- working-on-dotfilesSkill
- code-reviewSkill
The file
Files
Opening hunk
hunk needs a real terminal. The agent only prints the command, and the user pastes it in a new terminal or herdr tab.
Run
~/.agents/skills/opening-hunk/scripts/hunk-command.sh [path] [hunk args...]pathdefaults to the current directory and is resolved to the git toplevel, so a worktree shows its own diff.- The arguments default to
diff. Examples:diff --staged,show,diff main.
The first output line is context: local or context: ssh. Show the user the printed command as is.
What it prints
| Context | Command |
| Local | cd <path> && <hunk> diff |
| SSH | ssh -t [-p port] user@host 'cd <path> && <hunk> diff', to run on the machine the user connected from |
The host is the address from SSH_CONNECTION (SSH is otherwise detected from an sshd ancestor). Set HUNK_REMOTE_HOST to a host name or ssh alias when the laptop cannot resolve that address. The port from SSH_CONNECTION is then not added: the alias carries its own. In a herdr pane the variable can be missing or stale: if the user has several clients, confirm the host before relying on it.
The script exits 1 when hunk is not installed on this machine.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.