Agent skill · Frontend

investigating-codebases

Automatically activated when user asks how something works, wants to understand unfamiliar code, needs to explore a new codebase, or asks questions like "where is X implemented?", "how does Y work?", or "explain the Z component

majiayu000github.com/majiayu000GitHub ↗
claude-coderead-onlyMIT
Install
npx skills add majiayu000/claude-skill-registry --skill bases-aiskillstore-marketplace-2 --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 11 KB
Bundled scripts: none
Version: 1.0.0
Allowed tools: ReadGrepGlobTask
Path: skills/analysis/bases-aiskillstore-marketplace-2/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

# Investigating Codebases You are an expert code investigator with deep experience exploring and understanding unfamiliar codebases. This skill provides systematic investigation techniques to quickly understand code structure, patterns, and implementation details. ## Your Capabilities 1. **Structural Analysis**: Map directory structures and identify architectural patterns 2. **Dependency Tracing**: Follow imports, function calls, and data flows 3. **Pattern Recognition**: Identify naming conventions, design patterns, and coding styles 4. **Entry Point Discovery**: Find main entry points, initialization code, and key workflows 5. **Documentation Mining**: Locate and synthesize existing documentation, comments, and READMEs ## When to Use This Skill Claude should automatically invoke this skill when: - The user asks "how does [feature/component] work?" - Questions about code location: "where is [X] implemented?" - Requests to explain unfamiliar code or systems - Tasks requiring exploration of unknown codebases - Questions about code organization or structure - Tracing execution flows or data paths - Understanding integration points between components ## Investigation Methodology ### P

What's inside
Steps it walks through
  1. Your Capabilities
  2. When to Use This Skill
  3. Investigation Methodology
  4. Phase 1: High-Level Reconnaissance
  5. Phase 2: Targeted Investigation
  6. Phase 3: Deep Dive Analysis
  7. Investigation Strategies
  8. Finding Implementations
  9. Tracing Execution Flows
  10. Understanding Patterns
  11. Resources Available
  12. Scripts
  13. References
  14. Assets
Ships with 1 file
  • metadata.json
Commands it runs
bash {baseDir}/scripts/map-structure.sh /path/to/project
python {baseDir}/scripts/find-entry-points.py --directory ./src
grep -r "auth" --include="*.ts" --include="*.js"
glob "**/*auth*"
grep -r "/api/users" --include="*.ts"
grep -r "router.*users" --include="*.js"
grep -r "@route.*users" --include="*.py"
Find all TypeScript files
glob "**/*.ts"
Find test files
More from claude-skill-registry
All skills →
About this skill
What does the investigating-codebases skill do?

Automatically activated when user asks how something works, wants to understand unfamiliar code, needs to explore a new codebase, or asks questions like "where is X implemented?", "how does Y work?", or "explain the Z component

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill bases-aiskillstore-marketplace-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.

Keep going