agentleFS
Sign inStart free
woosikkimwoosikkim/oh-my-claudecode-slim/skills/deepinit/SKILL.md

deepinit

Skill1 starsChanged 9 months agoMITView on GitHub

Generate hierarchical AGENTS.md codebase maps for agent context

7 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ai-slop-cleaner, ralplan and 10 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.
  • Jurel89Skill

    ai-slop-cleaner

    Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode

    Also in 4 projects that use this

  • ibahgatSkill

    ralplan

    Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.

    Also in 3 projects that use this

  • klauswgSkill

    deep-interview

    在明确批准执行之前，通过数学化歧义门控进行苏格拉底式深度访谈

    Also in 3 projects that use this

  • thoughtbotSkill

    trace

    Run a scenario and record what actually happened.

    Also in 3 projects that use this

  • markmdevSkill

    self-improve

    Analyze Claude Code sessions to find workflow frictions, underused tools, stale instructions, documentation gaps, and opportunities for new skills or automation. Produces actionable improvement suggestions with prioritized recommendations. Use when the user says "self-improve", "analyze my workflow", "what can we improve", "find frictions", "optimize workflow", or asks about improving their Claude Code setup. Also suggest running this after long sessions, multi-session projects, or when the user seems frustrated with repetitive work.

    Also in 3 projects that use this

  • LangChainSkill

    remember

    Review the current conversation and capture valuable knowledge — best practices, coding conventions, architecture decisions, workflows, and user feedback — into persistent memory (AGENTS.md) or reusable skills. Use when the user says: (1) remember this, (2) save what we learned, (3) update memory, (4) capture learnings.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 2

    Distinctive

    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:

    If AGENTS.md files already exist, only regenerate for directories where files have changed since the last generation.

    line 34
  2. Distinctive:

    No generated files in excluded directories

    line 58

“Common” is measured: kept by at least 6 in 10 of the 6 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

Deepinit — Codebase Cartography

Generate hierarchical AGENTS.md files across a codebase to give agents architectural context without reading every file.

Steps

  1. Map directory structure using the explorer agent:
    • Discover all significant directories (exclude node_modules, .git, dist, build, coverage, .next, __pycache__)
    • Identify key source directories, config files, and entry points
  2. Generate root AGENTS.md with:
    • Project purpose (one sentence)
    • Tech stack summary
    • Top-level directory descriptions
    • Key entry points and config files
  3. Generate child AGENTS.md files for each significant subdirectory:
    • Purpose and role description
    • Key files with one-line descriptions
    • Subdirectories overview
    • Parent reference: <!-- Parent: ../AGENTS.md -->
  4. Work level-by-level — parents before children so child files can reference parent context
  5. Use the librarian agent for content generation (has full write access)

Update Mode

If AGENTS.md files already exist, only regenerate for directories where files have changed since the last generation.

Output Format

Each AGENTS.md follows this template:

<!-- Parent: ../AGENTS.md -->
# directory-name/

Brief purpose description.

## Key Files
- `file.ts` — One-line description
- `other.ts` — One-line description

## Subdirectories
- `sub/` — What this subdirectory contains

Success Criteria

  • Root AGENTS.md exists with project overview
  • Each significant directory has an AGENTS.md
  • Files are concise (under 30 lines each)
  • No generated files in excluded directories

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