Agent skill

file-analysis

- Before architecture reviews to understand module boundaries and file organization.'

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill file-analysis-athola-claude-night-market-b425baec --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 3 KB
Bundled scripts: none
Path: skills/analysis/file-analysis-athola-claude-night-market-b425baec/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

--- name: file-analysis description: | Triggers: codebase, file, analysis, structure, exploration Structured file enumeration and content analysis for understanding codebase structure before reviews or refactoring. Triggers: file analysis, codebase structure, directory mapping, hotspot detection, code exploration, file enumeration, structure mapping, module boundaries Use when: before architecture reviews to understand file organization, exploring unfamiliar codebases to map structure, estimating scope for refactoring or migration DO NOT use when: general code exploration - use the Explore agent. DO NOT use when: searching for specific patterns - use Grep directly. Provides structural context for downstream review and refactoring workflows. category: workspace-ops tags: [files, structure, analysis, codebase, exploration] tools: [Bash, Glob, Grep, TodoWrite] complexity: medium estimated_tokens: 800 dependencies: - sanctum:shared - imbue:evidence-logging --- # 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

What's inside
Steps it walks through
  1. When to Use
  2. Required TodoWrite Items
  3. Step 1: Identify Root (file-analysis:root-identified)
  4. Step 2: Map Structure (file-analysis:structure-mapped)
  5. Step 3: Detect Patterns (file-analysis:patterns-detected)
  6. Step 4: Note Hotspots (file-analysis:hotspots-noted)
  7. Exit Criteria
  8. Troubleshooting
  9. Common Issues
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the file-analysis skill do?

- Before architecture reviews to understand module boundaries and file organization.'

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill file-analysis-athola-claude-night-market-b425baec --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.

Keep going