How do I install the Read Codebase skill?

Run npx skillmds@latest add devitools/read-codebase in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Read Codebase safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Read Codebase?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Read Codebase free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Read Codebase?

devitools (@devitools) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Read Codebase by devitools — Agent Skill

Name: Read Codebase
Rating: 4.5 (4 reviews)
Author: devitools

Read Codebase

Explore and understand code structure efficiently using semantic navigation. Use when exploring unfamiliar code, understanding architecture, finding symbol relationships, or investigating how something works.

devitools 21c4e4f 3 files · 9.5 KB Updated Sep 17, 2026

File contents

Semantic Code Exploration

This skill guides efficient code exploration using Serena MCP for semantic navigation.

Prerequisite Check

Before proceeding, verify Serena is available by checking for mcp__serena__* tools.

If Serena is NOT configured: Tell the user: "This exploration would benefit from Serena MCP for semantic code navigation, but it's not configured. See .claude/skills/read-codebase/setup.md for installation instructions. Proceeding with standard tools (Grep/Read/Glob)."

Then use standard tools as fallback.

Tool Priority (when Serena is available)

get_symbols_overview - First step for any file
find_symbol - Locate specific classes/methods
find_referencing_symbols - Find all usages
search_for_pattern - When symbol name is unknown
read_memory - Check project knowledge (architecture, patterns)

Quick Reference

Understanding a File

get_symbols_overview(relative_path="path/to/file.php") → see structure
find_symbol(name_path_pattern="ClassName", depth=1) → see methods
Only use include_body=true for specific methods you need

Finding Where Code Is Used

find_symbol to locate the symbol
find_referencing_symbols to find all call sites

Exploring Unknown Code

Check memories: list_memories → read_memory("architecture")
Use search_for_pattern with keywords
Follow up with symbolic tools

Anti-Patterns

Reading entire files when you only need one method
Using Grep/Read when Serena tools would be more precise
Skipping symbol overview and going straight to file read
Not checking project memories for existing documentation

When to Use Standard Tools Instead

Simple text search across many files → Grep
Config files, markdown, non-code → Read
Known file needing full content → Read
Serena not configured → Fallback to Grep/Read/Glob

Additional Resources

Detailed workflows: workflows.md
Setup instructions: setup.md

---name: read-codebasedescription: Explore and understand code structure efficiently using semantic navigation. Use when exploring unfamiliar code, understanding architecture, finding symbol relationships, or investigating how something works.---# Semantic Code ExplorationThis skill guides efficient code exploration using **Serena MCP** for semantic navigation.## Prerequisite CheckBefore proceeding, verify Serena is available by checking for `mcp__serena__*` tools.**If Serena is NOT configured:**Tell the user: "This exploration would benefit from Serena MCP for semantic code navigation, but it's not configured. See `.claude/skills/read-codebase/setup.md` for installation instructions. Proceeding with standard tools (Grep/Read/Glob)."Then use standard tools as fallback.## Tool Priority (when Serena is available)1. **get_symbols_overview** - First step for any file2. **find_symbol** - Locate specific classes/methods3. **find_referencing_symbols** - Find all usages4. **search_for_pattern** - When symbol name is unknown5. **read_memory** - Check project knowledge (architecture, patterns)## Quick Reference### Understanding a File1. `get_symbols_overview(relative_path="path/to/file.php")` → see structure2. `find_symbol(name_path_pattern="ClassName", depth=1)` → see methods3. Only use `include_body=true` for specific methods you need### Finding Where Code Is Used1. `find_symbol` to locate the symbol2. `find_referencing_symbols` to find all call sites### Exploring Unknown Code1. Check memories: `list_memories` → `read_memory("architecture")`2. Use `search_for_pattern` with keywords3. Follow up with symbolic tools## Anti-Patterns- Reading entire files when you only need one method- Using Grep/Read when Serena tools would be more precise- Skipping symbol overview and going straight to file read- Not checking project memories for existing documentation## When to Use Standard Tools Instead- Simple text search across many files → Grep- Config files, markdown, non-code → Read- Known file needing full content → Read- Serena not configured → Fallback to Grep/Read/Glob## Additional Resources- Detailed workflows: [workflows.md](workflows.md)- Setup instructions: [setup.md](setup.md)

Frequently asked questions