agentleFS
Sign inStart free
modem-devmodem-dev/hunk/.agents/skills/hunk-extensions/SKILL.md

hunk-extensions

Skill9.8k starsChanged 19 days agoMITView on GitHub

Maps the `hunkdiff/extension` authoring surface for Hunk, the terminal diff viewer — hiding or reordering reviewed files, docked panes, alternate file views, commands and key bindings, dialogs, workspace writes, themes, syntax languages, VCS backends, lifecycle events. Use when writing, debugging, or installing a Hunk extension, or when a request asks Hunk itself to behave differently. Not for reviewing a diff in a live session — that is hunk-review.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about modem-dev/hunk

The biggest 5 of 70 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 70

Talked about on GitHub, Bluesky, the web and Hacker News (70 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 15

10 more on Bluesky

On the web · 3

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before anything else, load them and follow them:

    line 12
  2. Very specific:

    If hunk is not on PATH, ask the user to install Hunk first: https://hunk.dev/docs/start/install/

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- generated by `bun run generate:skill` -->

hunk-extensions

This file is a pointer. The instructions live in the installed hunk CLI so they always match its version.

Before anything else, load them and follow them:

hunk skill show hunk-extensions

Hunk versions before 0.24 do not have hunk skill show. If it fails, print the bundled skill's path instead, then read that file and follow it:

hunk skill path hunk-extensions

If hunk is not on PATH, ask the user to install Hunk first: https://hunk.dev/docs/start/install/

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free