🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί Codebase Explorer
πŸ¦€ ClawHub

Codebase Explorer

by @djc00p

Analyze unfamiliar codebases and generate structured onboarding guides with architecture maps, entry points, conventions, and project-specific instructions....

Versionv1.0.0
Downloads417
#legal#hr#travel
TERMINAL
clawhub install codebase-explorer

πŸ“– About This Skill

name: codebase-explorer description: "Analyze unfamiliar codebases and generate structured onboarding guides with architecture maps, entry points, conventions, and project-specific instructions. Use when joining new projects, understanding repo structure, or generating CLAUDE.md. Trigger phrases: onboard me, understand this codebase, analyze this repo, generate CLAUDE.md, walk me through. Adapted from everything-claude-code by @affaan-m (MIT)" metadata: {"clawdbot":{"emoji":"πŸ—ΊοΈ","requires":{"bins":[],"env":[]},"os":["darwin","linux","win32"]}}

Codebase Onboarding

Systematically analyze unfamiliar codebases and produce structured onboarding guides.

When to Use

  • First time opening a project
  • Joining a new team or repository
  • User asks "help me understand this codebase"
  • User asks to generate a CLAUDE.md for a project
  • User says "onboard me" or "walk me through this repo"

    • Quick Start

    1. Scan package manifests and config files (identify tech stack and framework) 2. Map directory structure and entry points (top 2 levels) 3. Trace one request lifecycle (entry β†’ validation β†’ business logic β†’ database) 4. Identify naming, error handling, and testing patterns 5. Generate onboarding guide and starter CLAUDE.md

    Key Concepts

  • Reconnaissance β€” Use file presence patterns to infer tech stack and structure
  • Architecture pattern β€” Identify monolith vs. monorepo, frontend/backend split, API style
  • Convention detection β€” Extract naming, error handling, async patterns from recent code
  • Guided exploration β€” Don't read everything; use grep/glob selectively for ambiguity
  • Two-artifact output β€” Onboarding guide (structure + conventions) + CLAUDE.md (project instructions)

    • Common Usage

    Most frequent patterns:

  • Understanding project structure and data flow
  • Documenting tech stack and architecture
  • Creating starter instructions for new team members
  • Identifying where to make changes (API routes, UI pages, database, tests)
  • Mapping conventions (naming, error handling, git workflow)

    • References

  • references/reconnaissance.md β€” File patterns for framework/language detection
  • references/artifacts.md β€” Onboarding guide and CLAUDE.md templates, best practices, anti-patterns

    • ⚑ When to Use

    TriggerAction
    - Joining a new team or repository
    - User asks "help me understand this codebase"
    - User asks to generate a CLAUDE.md for a project
    - User says "onboard me" or "walk me through this repo"

    πŸ’‘ Examples

    1. Scan package manifests and config files (identify tech stack and framework) 2. Map directory structure and entry points (top 2 levels) 3. Trace one request lifecycle (entry β†’ validation β†’ business logic β†’ database) 4. Identify naming, error handling, and testing patterns 5. Generate onboarding guide and starter CLAUDE.md