Agent skill · Security

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".

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill codebase-analysis-sequenzia-agent-alchemy-10 --agent claude-code

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

Facts
Files in the skill folder: 2
SKILL.md size: 23 KB
Bundled scripts: none
Requires: - deep-analysis - technical-diagrams
Path: skills/analysis/codebase-analysis-sequenzia-agent-alchemy-10/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.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

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 it works

  • Phase 1: Deep Analysis
    • Determine analysis context from provided arguments or default to general codebase understanding
    • Check for cached results in .agents/sessions/exploration-cache/manifest.md and validate codebase_path and timestamp against TTL
    • If cache is valid, offer to use cached results or run fresh analysis; set CACHE_HIT and CACHE_TIMESTAMP accordingly
    • If no valid cache, run deep-analysis workflow, passing the analysis context; after completion set CACHE_TIMESTAMP to null
    • Verify results, fill gaps if needed, and record metadata: CACHE_HIT, CACHE_TIMESTAMP, and number of explorer agents used (from team plan or 0 if cached)
  • Phase 2: Reporting
    • Load diagram guidance following technical-diagrams conventions and use Mermaid diagrams in Architecture Overview and Relationship Map
    • Structure report with sections: Executive Summary, Architecture Overview, Tech Stack, Critical Files, Patterns & Conventions, Relationship Map, Challenges & Risks, Recommendations, Analysis Methodology
  • Phase 3: Post-Analysis Actions
    • Prompt user to choose actions: Save Codebase Analysis Report, Save a custom report, Update project documentation, Keep a condensed summary in memory
    • For Save Codebase Analysis Report: determine file location, generate and save the report, confirm
    • For Save Custom Report: gather requirements, determine location, generate and save per requirements
    • For Update Project Documentation: select files (README.md, CLAUDE.md, AGENTS.md), gather directions, generate drafts, present drafts, apply or revise
    • For Keep Insights in Memory: present a Codebase Quick Reference in conversation only
  • Step 3: Actionable Insights Follow-up (always executes): extract items from Phase 2, present severity-ranked list, and allow user to address items in priority order with structured planning, approval, and execution prompts

When to use it

Use when user asks to analyze or understand a codebase, map its structure, or audit it; triggers include phrases like "analyze codebase", "explore codebase", "understand this codebase", or "codebase report".

What it can touch

  • Tools: claude-code (as declared)
  • Artifacts: Phase 2 report findings, Phase 3 actionables, documentation drafts, updated files if approved

Caveats

  • License: MIT
  • Requires: - deep-analysis - technical-diagrams
  • Dependency on deep-analysis for orchestration and agent coordination; results may depend on upstream agent outputs
  • Cache mechanism relies on filesystem paths and TTL; behavior described only as specified
From the SKILL.md

# Codebase Analysis Workflow Execute a structured 3-phase codebase analysis workflow to gather insights. ## Phase Overview 1. **Deep Analysis** -- Explore and synthesize codebase findings via the 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 are provided, use them as the analysis context - If no arguments, set context to "general codebase understanding" 2. **Check for cached results:** - Check if `.agents/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**, prompt the user to choose: - **Use cached results** (show the formatted cache date) -- Read cached synthesis from `.agents/sessions/exploration-cache/synthesis.md` and recon from `recon_summary.md`. Set `CACHE_HIT = true` and `CACHE_TIMESTAMP` to the cache's timestamp. Skip step 3 and proceed directly to

What's inside
Steps it walks through
  1. Phase Overview
  2. Phase 1: Deep Analysis
  3. Phase 2: Reporting
  4. Phase 3: Post-Analysis Actions
  5. Step 1: Select actions
  6. Step 2: Execute selected actions
  7. Step 3: Actionable Insights Follow-up
  8. Step 4: Complete the workflow
  9. Error Handling
  10. General
  11. Documentation Update Failures (Step 2c)
  12. Agent Delegation Failures (Step 3c)
  13. Agent Coordination
  14. Report Template
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
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-10 --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
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.