codebase-analysis
Produce a structured codebase analysis report with architecture overview, critical files, patterns, and actionable recommendations. Use when asked to "analyze codebase", "explore codebase", "understand this codebase", "map the codebase", "give me an overview of this project", "what does this codebase do", "codebase report", "project analysis", "audit this codebase", or "how is this project structured".
npx skills add majiayu000/claude-skill-registry --skill codebase-analysis-sequenzia-agent-alchemy --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.
# Codebase Analysis Workflow Execute a structured 3-phase codebase analysis workflow to gather insights. **CRITICAL: Complete ALL 3 phases.** The workflow is not complete until Phase 3: Post-Analysis Actions is finished. After completing each phase, immediately proceed to the next phase without waiting for user prompts. ## Phase Overview 1. **Deep Analysis** — Explore and synthesize codebase findings via deep-analysis skill 2. **Reporting** — Present structured analysis to the user 3. **Post-Analysis Actions** — Save, document, or retain analysis insights --- ## Phase 1: Deep Analysis **Goal:** Explore the codebase and synthesize findings. 1. **Determine analysis context:** - If `$ARGUMENTS` is provided, use it as the analysis context - If no arguments, set context to "general codebase understanding" 2. **Check for cached results:** - Check if `.claude/sessions/exploration-cache/manifest.md` exists - If found, read the manifest and verify: `codebase_path` matches the current working directory, and `timestamp` is within the configured cache TTL (default 24 hours) - **If cache is valid**, use `AskUserQuestion`: - **Use cached results** (show the formatted cache date) — Read cached sy
- Phase Overview
- Phase 1: Deep Analysis
- Phase 2: Reporting
- Phase 3: Post-Analysis Actions
- Step 1: Select actions
- Step 2: Execute selected actions
- Step 3: Actionable Insights Follow-up
- Step 4: Complete the workflow
- Error Handling
- General
- Documentation Update Failures (Step 2c)
- Agent Launch Failures (Step 3c)
- Agent Coordination
- Additional Resources
What does the codebase-analysis skill do?
Produce a structured codebase analysis report with architecture overview, critical files, patterns, and actionable recommendations. Use when asked to "analyze codebase", "explore codebase", "understand this codebase", "map the codebase", "give me an overview of this project", "what does this codebase do", "codebase report", "project analysis", "audit this codebase", or "how is this project structured".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill codebase-analysis-sequenzia-agent-alchemy --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.