file-analysis
Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation.
npx skills add majiayu000/claude-skill-registry --skill file-analysis-athola-claude-night-market-2 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# File Analysis ## When To Use - Before architecture reviews to understand module boundaries and file organization. - When exploring unfamiliar codebases to map structure before making changes. - As input to scope estimation for refactoring or migration work. ## When NOT To Use - General code exploration - use the Explore agent - Searching for specific patterns - use Grep directly ## Required TodoWrite Items 1. `file-analysis:root-identified` 2. `file-analysis:structure-mapped` 3. `file-analysis:patterns-detected` 4. `file-analysis:hotspots-noted` Mark each item as complete as you finish the corresponding step. ## Step 1: Identify Root (`file-analysis:root-identified`) - Confirm the analysis root directory with `pwd`. - Note any monorepo boundaries, workspace roots, or subproject paths. - Capture the project type (language, framework) from manifest files (`package.json`, `Cargo.toml`, `pyproject.toml`, etc.). ## Step 2: Map Structure (`file-analysis:structure-mapped`) - Run `tree -L 2 -d` or `find . -type d -maxdepth 2` to capture the top-level directory layout. - Identify standard directories: `src/`, `lib/`, `tests/`, `docs/`, `scripts/`, `configs/`. - Note any non-standard organ
- When To Use
- When NOT To Use
- Required TodoWrite Items
- Step 1: Identify Root (file-analysis:root-identified)
- Step 2: Map Structure (file-analysis:structure-mapped)
- Step 3: Detect Patterns (file-analysis:patterns-detected)
- Step 4: Note Hotspots (file-analysis:hotspots-noted)
- Exit Criteria
What does the file-analysis skill do?
Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill file-analysis-athola-claude-night-market-2 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.