Skill

codebase-walkthrough

Deep dive into codebase architecture, key modules, and design patterns. Use when user says "codebase walkthrough", "show me the code", or "architecture overview".

Install

npx claudepluginhub monty1985/adams-mind --plugin onboard-codebase-walkthrough

Tool Access

This skill uses the workspace's default tool permissions.

Preview

- Describe the overall system architecture (monolith, microservices, monorepo, etc.)

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.2k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

smart-explore

Performs token-optimized structural code search using tree-sitter AST parsing to discover symbols, outline files, and unfold code without reading full files.

claude-mem

65.8k

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitApr 1, 2026

Actions

View Source View Plugin View on GitHub View README

Codebase Walkthrough

Phase 1: High-Level Architecture

Describe the overall system architecture (monolith, microservices, monorepo, etc.)

Map the major services and how they communicate (REST, gRPC, events, queues)

Explain the data flow from user action to database and back

Identify the infrastructure layer (cloud provider, containers, CDN, CI/CD)

Phase 2: Key Modules

Tour the most important directories and their responsibilities

Highlight the core domain logic and where business rules live

Walk through the API layer: routing, middleware, controllers, validation

Explain the data access layer: ORM, query patterns, migration strategy

Point out shared utilities, design systems, and internal libraries

Phase 3: Patterns & Conventions

Explain the primary design patterns in use (MVC, repository, CQRS, etc.)

Review coding conventions: naming, file structure, error handling, logging

Walk through the testing strategy and where tests live

Highlight any known technical debt and areas earmarked for refactoring

Share links to Architecture Decision Records (ADRs) for key past decisions