agentleFS
ArcticFox2029ArcticFox2029/chamnan/skills/remap/SKILL.md

remap

Skill10 starsChanged 7 days agoMITView on GitHub

Rebuild the architecture index after files were added, removed, renamed, or restructured. Cheap to run; run it whenever the shape of the repo changed rather than waiting to be asked.

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:

    Run this after any change to the repo's *shape* — new module, deleted file, renamed directory, a function moved somewhere else.

    line 11
  2. Very specific:

    If the described-coverage percentage fell, new files arrived without an opening comment.

    line 18

≈ “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

Refresh the index

chamnan-map

Run this after any change to the repo's shape — new module, deleted file, renamed directory, a function moved somewhere else. Not after every edit; the index describes structure, and editing the body of a function does not change structure.

A stale index is worse than none. It is confidently wrong, and the next session will believe it and open the file that no longer holds what it says.

If the described-coverage percentage fell, new files arrived without an opening comment. Say which ones. Read agents from .chamnan/config.json (default true) first — with false, name the files and leave them to the user. Otherwise offer the chamnan:commenter agent (the plugin-scoped name, so a second installed plugin that also ships a commenter cannot be picked instead), wait for the go-ahead, and tell it which language to write in from language (default en) — the agent writes English unless named, so bootstrap passes it explicitly and this path must too.

chamnan-map --undocumented is where the full list comes from — one path per line, all of them. The rebuild's own output names at most eight, as examples; a session that treats those eight as the list will fix eight and report the gap as closed.

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.