# analyze-codebase

> Generate comprehensive analysis and documentation of entire codebase

- Author: LiamWang
- Repository: YPYT1/Liamblog
- Version: 20260113223256
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-07
- Source: https://github.com/YPYT1/Liamblog
- Web: https://mule.run/skillshub/@@YPYT1/Liamblog~analyze-codebase:20260113223256

---

---
name: analyze-codebase
description: Generate comprehensive analysis and documentation of entire codebase
version: 1.0.0
author:  Anand Tyagi
source: Claude Code Marketplace
keywords: explore, plan
---

# analyze-codebase

Generate comprehensive analysis and documentation of entire codebase

## 来源信息

- **原始平台**: Claude Code
- **市场来源**: Claude Code Marketplace
- **原始名称**: analyze-codebase
- **版本**: 1.0.0
- **作者**:  Anand Tyagi
- **关键词**: explore, plan

## 功能描述

# Comprehensive Codebase Analysis
## Project Discovery Phase
### Directory Structure
!`find . -type d -not -path "./node_modules/*" -not -path "./.git/*" -not -path "./dist/*" -not -path "./build/*" -not -path "./.next/*" -not -path "./coverage/*"`
### Complete File Tree
!`find . -type f -not -path "./node_modules/*" -not -path "./.git/*" -not -path "./dist/*" -not -path "./build/*" -not -path "./.next/*" -not -path "./coverage/*" -not -path "./*.log"`
### File Count and Size Analysis
- Total files: !`find . -type f -not -path "./node_modules/*" -not -path "./.git/*"`
- Code files: !`find . -not -path "./node_modules/*" -not -path "./.git/*" \( -name "*.js" -o -name "*.ts" -o -name "*.jsx" -o -name "*.tsx" -o -name "*.py" -o -name "*.java" -o -name "*.php" -o -name "*.rb" -o -name "*.go" -o -name "*.rs" -o -name "*.cpp" -o -name "*.c" \)`
- Project size: !`du -sh .`
## Configuration Files Analysis
### Package Management
- Package.json: @package.json
- Package-lock.json exists: !`find . -maxdepth 1 -name "package-lock.json"`
- Yarn.lock exists: !`find . -maxdepth 1 -name "yarn.lock"`
- Requirements.txt: @requirements.txt
- Gemfile: @Gemfile
- Cargo.toml: @Cargo.toml
- Go.mod: @go.mod
- Composer.json: @composer.json
### Build & Dev Tools
- Webpack config: @webpack.config.js
- Vite config: @vite.config.js
- Rollup config: @rollup.config.js
- Babel config: @.babelrc
- ESLint config: @.eslintrc.js
- Prettier config: @.prettierrc
- TypeScript config: @tsconfig.json
- Tailwind config: @tailwind.config.js
- Next.js config: @next.config.js
### Environment & Docker
- .env files: !`find . -name ".env*" -type f`
- Docker files: !`find . -name "Dockerfile*" -o -name "docker-compose*"`
- Kubernetes files: !`find . -type f \( -name "*k8s*.yaml" -o -name "*k8s*.yml" -o -name "*kubernetes*.yaml" -o -name "*kubernetes*.yml" -o -name "*deployment*.yaml" -o -name "*deployment*.yml" \)`
### CI/CD Configuration
- GitHub Actions: !`find .github -type f \( -name "*.yml" -o -name "*.yaml" \)`
- GitLab CI: @.gitlab-ci.yml
- Travis CI: @.travis.yml
- Circle CI: @.circleci/config.yml
## Source Code Analysis
### Main Application Files
- Main entry points: !`find . -not -path "./node_modules/*" -not -path "./.git/*" \( -name "main.*" -o -name "index.*" -o -name "app.*" -o -name "server.*" \)`
- Routes/Controllers: !`find . -not -path "./node_modules/*" -not -path "./.git/*" \( -path "*/routes/*" -o -path "*/controllers/*" -o -path "*/api/*" \)`
- Models/Schemas: !`find . -not -path "./node_modules/*" -not -path "./.git/*" \( -path "*/models/*" -o -path "*/schemas/*" -o -path "*/entities/*" \)`
- Components: !`find . -not -path "./node_modules/*" -not -path "./.git/*" \( -path "*/components/*" -o -path "*/views/*" -o -path "*/pages/*" \)`
### Database & Storage
- Database configs: !`find . -not -path "./node_modules/*" -not -path "./.git/*" \( -name "*database*" -o -name "*db*" -o -name "*connection*" \)`
- Migration files: !`find . -not -path "./node_modules/*" -not -path "./.git/*" \( -path "*/migrations/*" -o -path "*/migrate/*" \)`
- Seed files: !`find . -not -path "./node_modules/*" -not -path "./.git/*" \( -path "*/seeds/*" -o -path "*/seeders/*" \)`
### Testing Files
- Test files: !`find . -not -path "./node_modules/*" -not -path "./.git/*" \( -name "*test*" -o -name "*spec*" \)`
- Test config: @jest.config.js
### API Documentation
- API docs: !`find . -not -path "./node_modules/*" -not -path "./.git/*" \( -name "*api*.md" -o -name "swagger*" -o -name "openapi*" \)`
## Key Files Content Analysis
### Root Configuration Files
@README.md
@LICENSE
@.gitignore
### Main Application Entry Points
!`find . -not -path "./node_modules/*" -not -path "./.git/*" \( -name "index.js" -o -name "index.ts" -o -name "main.js" -o -name "main.ts" -o -name "app.js" -o -name "app.ts" -o -name "server.js" -o -name "server.ts" \)`
## Your Task
Based on all the discovered information above, create a comprehensive analysis that includes:
## 1. Project Overview
- Project type (web app, API, library, etc.)
- Tech stack and frameworks
- Architecture pattern (MVC, microservices, etc.)
- Language(s) and versions
## 2. Detailed Directory Structure Analysis
For each major directory, explain:
- Purpose and role in the application
- Key files and their functions
- How it connects to other parts
## 3. File-by-File Breakdown
Organize by category:
- **Core Application Files**: Main entry points, routing, business logic
- **Configuration Files**: Build tools, environment, deployment
- **Data Layer**: Models, database connections, migrations
- **Frontend/UI**: Components, pages, styles, assets
- **Testing**: Test files, mocks, fixtures
- **Documentation**: README, API docs, guides
- **DevOps**: CI/CD, Docker, deployment scripts
## 4. API Endpoints Analysis
If applicable, document:
- All discovered endpoints and their methods
- Authentication/authorization patterns
- Request/response formats
- API versioning strategy
## 5. Architecture Deep Dive
Explain:
- Overall application architecture
- Data flow and request lifecycle
- Key design patterns used
- Dependencies between modules
## 6. Environment & Setup Analysis
Document:
- Required environment variables
- Installation and setup process
- Development workflow
- Production deployment strategy
## 7. Technology Stack Breakdown
List and explain:
- Runtime environment
- Frameworks and libraries
- Database technologies
- Build tools and bundlers
- Testing frameworks
- Deployment technologies
## 8. Visual Architecture Diagram
Create a comprehensive diagram showing:
- High-level system architecture
- Component relationships
- Data flow
- External integrations
- File structure hierarchy
Use ASCII art, mermaid syntax, or detailed text representation to show:
┌─────────────────┐     ┌─────────────────┐     ┌─────────────────┐
│     Frontend    │────>│      API        │────>│    Database     │
│   (React/Vue)   │     │   (Node/Flask)  │     │ (Postgres/Mongo)│
└─────────────────┘     └─────────────────┘     └─────────────────┘
## 9. Key Insights & Recommendations
Provide:
- Code quality assessment
- Potential improvements
- Security considerations
- Performance optimization opportunities
- Maintainability suggestions
Think deeply about the codebase structure and provide comprehensive insights that would be valuable for new developers joining the project or for architectural decision-making.
At the end, write all of the output into a file called "codebase_analysis.md"

## 使用方法

1. **自动触发**: Codex 会根据任务描述自动选择并使用此技能
2. **手动指定**: 在提示中提及技能名称或相关关键词
3. **斜杠命令**: 使用 `/skills` 命令查看并选择可用技能

## 兼容性

- ✅ Codex CLI
- ✅ Codex IDE 扩展
- ✅ 基于 Agent Skills 开放标准

---
*此技能由 Claude Code 插件自动转换，已适配 Codex 官方技能系统*