agentleFS
Sign inStart free
vidit19sharmavidit19sharma/neogents/skills/map/SKILL.md

map

Skill1 starsChanged 11 days agoMITView on GitHub

Deep codebase mapping. Fans out parallel exploration recon across an existing repository and has neo-shadow synthesize the findings into ARCHITECTURE.md. Use when adopting NEO in a mature codebase, when ARCHITECTURE.md is empty or stale, or when the user asks to map or document the codebase structure.

31 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ultragoal, cost and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Yeachan-HeoSkill

    ultragoal

    Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.

    Also in 3 projects that use this

  • maxvaegaSkill

    cost

    Estimate what Claude Cowork / Claude Code conversations would cost if run on the pay-per-token Claude API instead of the subscription. Reports token counts and cache-aware API cost in USD and EUR, for the current conversation or for the whole history (cost per conversation). Trigger when the user asks things like "how much would this conversation cost on the API", "API cost of my Cowork conversations", "token usage / token count", "cost per conversation", "/cost", or wants to compare subscription vs API pricing.

    Also in 3 projects that use this

  • marylinSkill

    recover

    Recover work from a crashed or interrupted session. Use when Claude crashed mid-task, after an unexpected exit, when you see 'stale sessions detected', or when you lost context and need to figure out what was happening.

    Also in 3 projects that use this

  • thoughtbotSkill

    trace

    Run a scenario and record what actually happened.

    Also in 4 projects that use this

  • POSTTTTSkill

    tidy

    Clean up and organize a project's file structure — group loose files into logical folders (images/, scripts/, styles/, etc.), remove empty directories, and delete genuinely unnecessary files. Use when the user asks to "clean up the project", "organize the files", "tidy the directory", "sort these into folders", "remove empty folders", or "get rid of junk files". Always understands the project and updates references BEFORE moving anything, never deletes load-bearing files, and gets approval before changing the file tree.

    Also in 3 projects that use this

  • HeshamFSSkill

    loop

    Run a command or check on a recurring interval

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    If graphify is available and a graph.json exists, tell each recon agent to prefer graphify query/path/explain over broad grep.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “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

/neo:map — map the codebase into ARCHITECTURE.md

Build or refresh the second brain's map of this codebase.

Current state

  • Brain: !ls -q .neo/brain 2>/dev/null || echo "MISSING"
  • ARCHITECTURE.md size: !if test -f .neo/brain/ARCHITECTURE.md && test ! -L .neo/brain/ARCHITECTURE.md; then head -c 1048576 .neo/brain/ARCHITECTURE.md | wc -l | tr -d ' '; else echo "n/a"; fi
  • Graphify: !command -v graphify >/dev/null 2>&1 && echo "available" || echo "not installed"

Steps

  1. Guard. No .neo/brain/ → stop and suggest /neo:init first. This command fills the map; init builds the shelf.

  2. Recon fan-out. Spawn built-in exploration subagents IN PARALLEL (one message, 3–4 spawns), each with the full 6-section contract and ONE angle:

    • Stack & entry points: languages, frameworks + versions from manifests, build/test/lint commands, where execution starts.
    • Layout & boundaries: top-level modules, what owns what, how layers talk (imports, APIs, events).
    • Patterns & conventions: error handling, naming, state management, test conventions — concrete one-liners with file:line examples.
    • Gotchas & hotspots: the biggest files, circular-looking dependencies, anything where "X looks like Y but is actually Z".

    If graphify is available and a graph.json exists, tell each recon agent to prefer graphify query/path/explain over broad grep.

  3. Synthesize via shadow. Spawn neo-shadow with ALL recon findings as the delta. Contract: rewrite ARCHITECTURE.md (Stack / Layout / Patterns / Gotchas — concrete, file-anchored, no prose padding); extract any subsystem too big for a section into .neo/brain/topics/<name>.md and [[wiki-link]] it; update INDEX.md pointers; touch nothing else.
  4. Report. Tell the user what the map now covers, its size (flag if ARCHITECTURE.md pushed past ~500 lines — shadow should have split topics), and anything the recon flagged as unclear or contradictory.

Re-running is safe: shadow rewrites from current findings, and prior knowledge lives in git history.

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