agentleFS
Sign inStart free
patrickbdevaneypatrickbdevaney/hermes-max/skills/workflow-repomap/SKILL.md

workflow-repomap

Skill1 starsChanged 6 months agoMITView on GitHub

Use repo_map at the START of a coding task to orient to an unfamiliar codebase structure. Pass the files you plan to edit as focus_files. The map ranks the most structurally important symbols (PageRank over the call/def graph) and their relationships — use it to find the relevant classes/functions before reading whole files. Trigger when entering a new repo or subsystem you haven't mapped yet.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the ranked symbols to find the classes/functions that matter, then open only those files — instead of blindly reading the tree.

    line 31

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

workflow-repomap

<!-- TRIGGERS WHEN: starting work in an unfamiliar repo/subsystem, before reading full files -->

repo_map(repo_path, focus_files, token_budget) (mcp-repomap) returns Aider's PageRank repo-map: the most structurally central symbols in the repo, ranked by how connected they are in the tree-sitter symbol graph. It answers "what's the important code I haven't been told about?" — a different question from the other two context tools, and best used together:

ToolQuestion it answers
search_code (RAG)"what is semantically similar to my query?"
lsp_* (LSP)"where exactly is this symbol defined / used?"
repo_map"what is structurally most important here?"

How

  1. At task start, call repo_map(repo_path="<repo>", focus_files=[<files you'll edit>]). focus_files bias the ranking toward what's relevant to your task (weighted 50×).
  2. Read the ranked symbols to find the classes/functions that matter, then open only those files — instead of blindly reading the tree.
  3. The map is cached 60s (structure changes slowly); re-call with different focus_files as your edit target shifts.

Pure static analysis — no model call, fast. Degrades to nothing if the server is down (fall back to search_code + reading files).

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