Codebase analysis skills consiliency codebase analysis
Skill bg-szy/TOP-SKILLS/skills/marketplace/codebase-analysis__skills-consiliency-codebase-analysis
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill codebase-analysis__skills-consiliency-codebase-analysisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Patterns and techniques for analyzing brownfield codebases. Use when onboarding to unfamiliar code, preparing for refactoring, conducting architecture reviews, or identifying technical debt.
SKILL.md
3.6 KB, as published. Nobody here has run it
Codebase Analysis Skill
Systematically explore and understand existing codebases, including entry point discovery, dependency tracing, pattern detection, and technical debt identification.
Variables
| Variable | Default | Description |
|---|---|---|
| ANALYSIS_DEPTH | standard | quick (5min), standard (30min), deep (1hr+) |
| OUTPUT_FORMAT | markdown | markdown, json, c4 |
| INCLUDE_DEBT | true | Include technical debt assessment |
| INCLUDE_DIAGRAMS | true | Generate C4 diagrams |
Instructions
MANDATORY - Follow the Workflow steps below in order. Do not skip steps.
- Start with entry points, not random files
- Trace dependencies before analyzing patterns
- Document findings as you go
Red Flags - STOP and Reconsider
If you're about to:
- Analyze random files without finding entry points first
- Make architectural claims without tracing dependencies
- Skip pattern detection before identifying anti-patterns
- Report technical debt without severity classification
STOP -> Read the appropriate cookbook file -> Follow the workflow -> Then proceed
Workflow
- Quick Assessment: Project size, structure, config files
- CHECKPOINT: Identify entry points (read
cookbook/entry-point-discovery.md) - Trace dependencies from entry points
- Detect architectural patterns
- CHECKPOINT: Verify pattern detection before anti-pattern search
- Identify anti-patterns and technical debt
- Document findings with C4 diagrams (if INCLUDE_DIAGRAMS)
Cookbook
Entry Point Discovery
- IF: Starting analysis of unfamiliar codebase
- THEN: Read
cookbook/entry-point-discovery.md - RESULT: List of main entry points by framework
Dependency Tracing
- IF: Need to understand how modules connect
- THEN: Read
cookbook/dependency-tracing.md - RESULT: Import chains, dependency graph
Pattern Detection
- IF: Need to identify architectural style
- THEN: Read
cookbook/pattern-detection.md - RESULT: Identified patterns (MVC, Layered, etc.)
Technical Debt Identification
- IF: Assessing code quality and debt
- THEN: Read
cookbook/debt-identification.md - RESULT: Prioritized debt inventory
Quick Reference
Entry Points by Stack
| Stack | Look For |
|---|---|
| Node.js | package.json main/bin, index.js, server.js |
| TypeScript | tsconfig.json, src/index.ts |
| Python | __main__.py, app.py, wsgi.py |
| Go | main.go, cmd/*/main.go |
| React | src/index.tsx, pages/_app.tsx |
See reference/framework-patterns.md for complete list.
Common Patterns
| Pattern | Directory Signs |
|---|---|
| MVC | models/, views/, controllers/ |
| Layered | presentation/, business/, data/ |
| Hexagonal | domain/, ports/, adapters/ |
| Microservices | services/*/, packages/*/ |
Output
Standard Report Format
# Codebase Analysis: [Project Name]
## Overview
- **Size**: X files, Y lines
- **Primary Language**: TypeScript
- **Framework**: Next.js
- **Architecture**: [Pattern]
## Entry Points
1. `src/pages/_app.tsx` - Application root
2. `src/api/` - API routes
## Key Dependencies
- [External deps list]
## Architecture Diagram
[C4 diagram if INCLUDE_DIAGRAMS]
## Technical Debt (if INCLUDE_DEBT)
| Issue | Severity | Location |
|-------|----------|----------|
| ... | High | ... |