file-analysis

Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation.

Jump to install

Repository: athola/claude-night-market
Last source activity: June 20, 2026 at 17:11
Detected SKILL.md language: English
Stars: 327
Forks: 35

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/athola/claude-night-market --skill file-analysis

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

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

file-analysis:root-identified
file-analysis:structure-mapped
file-analysis:patterns-detected
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 organization patterns that may affect downstream analysis.

Step 3: Detect Patterns (`file-analysis:patterns-detected`)

Use find . -name "*.ext" -not -path "*/.venv/*" -not -path "*/__pycache__/*" -not -path "*/node_modules/*" -not -path "*/.git/*" | wc -l to count files by extension.
Identify dominant languages and their file distributions.
Note configuration files, generated files, and vendored dependencies.
Run wc -l $(find . -not -path "*/.venv/*" -not -path "*/__pycache__/*" -not -path "*/node_modules/*" -not -path "*/.git/*" -name "*.py" -o -name "*.rs" | head -20) to sample file sizes.

Step 4: Note Hotspots (`file-analysis:hotspots-noted`)

Identify large files (potential "god objects"): find . -type f -exec wc -l {} + | sort -rn | head -10.
Flag deeply nested directories that may indicate complexity.
Note files with unusual naming conventions or placement.

Exit Criteria

TodoWrite items are completed with concrete observations.
Downstream workflows (architecture review, refactoring) have structural context.
File counts, directory layout, and hotspots are documented for reference.

name	file-analysis
description	Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation.
alwaysApply	false
category	workspace-ops
tags	["files","structure","analysis","codebase","exploration"]
tools	[]
complexity	medium
model_hint	standard
estimated_tokens

name	file-analysis
description	Maps file structure and module organization of a codebase. Use before architecture reviews, refactoring planning, or migration scope estimation.
alwaysApply	false
category	workspace-ops
tags	["files","structure","analysis","codebase","exploration"]
tools	[]
complexity	medium
model_hint	standard
estimated_tokens

file-analysis

Source facts