Codebase Consolidation & Analysis
Systematically analyze codebases to identify consolidation opportunities, document architecture, and generate actionable insights.
Quick Reference
- Analysis Dimensions - 8 analysis dimensions with detailed criteria
- Consolidation Patterns - Common refactoring patterns with examples
- Report Templates - Output format templates
When to Use
- Starting on a new codebase - Understand structure quickly
- Planning refactoring - Identify consolidation opportunities
- Code review preparation - Comprehensive analysis before changes
- Documentation needs - Generate architecture docs
- Technical debt assessment - Quantify and prioritize improvements
- Onboarding new developers - Create codebase overview
- Pre-release audits - Quality and security review
Don't use for: Single file analysis, quick bug fixes, simple feature additions
Core Purpose
Comprehensive codebase analysis:
- Code Duplication - Find duplicate code for consolidation
- Architectural Analysis - Document system structure and patterns
- Refactoring Opportunities - Identify improvement areas
- Technical Debt Assessment - Quantify and prioritize debt
- Documentation Generation - Create architecture diagrams and docs
- Multi-Perspective Analysis - Review from architect, developer, product views
- Quality Metrics - Complexity, coverage, maintainability
Analysis Dimensions
| Dimension |
Focus |
| Code Duplication |
Find duplicate/similar code blocks |
| Architectural Structure |
System architecture and component relationships |
| Code Organization |
Module structure and separation of concerns |
| Refactoring Opportunities |
Large files, complex functions |
| Technical Debt |
TODOs, missing tests, outdated deps |
| Quality Metrics |
LOC, complexity, coverage |
| Design Patterns |
Patterns and anti-patterns in use |
| Cross-Cutting Concerns |
Error handling, logging, security |
See analysis-dimensions.md for detailed criteria.
Analysis Workflow
- Discovery - Project structure, file counts, configuration
- Dependency Analysis - cargo tree, outdated, audit
- Duplication Detection - Large files, tech debt markers
- Complexity Analysis - LOC statistics, long functions
- Architecture Mapping - Components, dependencies, data flow
- Quality Assessment - Coverage, linting, formatting
- Documentation Review - Doc generation, API documentation
- Synthesis - Comprehensive report with recommendations
Output Formats
- Executive Summary - Health score, key metrics, priorities
- Architecture Documentation - System diagram, patterns, data flows
- Refactoring Roadmap - Phased plan with tasks and estimates
- Technical Debt Report - Quantified debt, payoff strategy
- Onboarding Document - Developer guide to codebase
See report-templates.md for complete templates.
Best Practices
✓ Start with high-level structure, use automated tools, prioritize findings, provide concrete examples with file paths, estimate effort, consider multiple perspectives
✗ Don't analyze without clear goals, only report problems, provide generic advice, ignore context, recommend big rewrites, overwhelm with detail
See consolidation-patterns.md for refactoring patterns and examples.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: codebase-consolidation3description: Analyze, consolidate, and document codebases through multi-perspective analysis. Use when reviewing project structure, planning refactoring, creating documentation, or assessing technical debt. Use when this capability is needed.4---56# Codebase Consolidation & Analysis78Systematically analyze codebases to identify consolidation opportunities, document architecture, and generate actionable insights.910## Quick Reference1112- **[Analysis Dimensions](analysis-dimensions.md)** - 8 analysis dimensions with detailed criteria13- **[Consolidation Patterns](consolidation-patterns.md)** - Common refactoring patterns with examples14- **[Report Templates](report-templates.md)** - Output format templates1516## When to Use1718- Starting on a new codebase - Understand structure quickly19- Planning refactoring - Identify consolidation opportunities20- Code review preparation - Comprehensive analysis before changes21- Documentation needs - Generate architecture docs22- Technical debt assessment - Quantify and prioritize improvements23- Onboarding new developers - Create codebase overview24- Pre-release audits - Quality and security review2526**Don't use for**: Single file analysis, quick bug fixes, simple feature additions2728## Core Purpose2930Comprehensive codebase analysis:31- **Code Duplication** - Find duplicate code for consolidation32- **Architectural Analysis** - Document system structure and patterns33- **Refactoring Opportunities** - Identify improvement areas34- **Technical Debt Assessment** - Quantify and prioritize debt35- **Documentation Generation** - Create architecture diagrams and docs36- **Multi-Perspective Analysis** - Review from architect, developer, product views37- **Quality Metrics** - Complexity, coverage, maintainability3839## Analysis Dimensions4041| Dimension | Focus |42|-----------|-------|43| Code Duplication | Find duplicate/similar code blocks |44| Architectural Structure | System architecture and component relationships |45| Code Organization | Module structure and separation of concerns |46| Refactoring Opportunities | Large files, complex functions |47| Technical Debt | TODOs, missing tests, outdated deps |48| Quality Metrics | LOC, complexity, coverage |49| Design Patterns | Patterns and anti-patterns in use |50| Cross-Cutting Concerns | Error handling, logging, security |5152See **[analysis-dimensions.md](analysis-dimensions.md)** for detailed criteria.5354## Analysis Workflow55561. **Discovery** - Project structure, file counts, configuration572. **Dependency Analysis** - cargo tree, outdated, audit583. **Duplication Detection** - Large files, tech debt markers594. **Complexity Analysis** - LOC statistics, long functions605. **Architecture Mapping** - Components, dependencies, data flow616. **Quality Assessment** - Coverage, linting, formatting627. **Documentation Review** - Doc generation, API documentation638. **Synthesis** - Comprehensive report with recommendations6465## Output Formats6667- **Executive Summary** - Health score, key metrics, priorities68- **Architecture Documentation** - System diagram, patterns, data flows69- **Refactoring Roadmap** - Phased plan with tasks and estimates70- **Technical Debt Report** - Quantified debt, payoff strategy71- **Onboarding Document** - Developer guide to codebase7273See **[report-templates.md](report-templates.md)** for complete templates.7475## Best Practices7677✓ Start with high-level structure, use automated tools, prioritize findings, provide concrete examples with file paths, estimate effort, consider multiple perspectives7879✗ Don't analyze without clear goals, only report problems, provide generic advice, ignore context, recommend big rewrites, overwhelm with detail8081See **[consolidation-patterns.md](consolidation-patterns.md)** for refactoring patterns and examples.8283---84> Converted and distributed by [TomeVault](https://tomevault.io/claim/d-o-hub) — claim your Tome and manage your conversions.85<!-- tomevault:4.0:skill_md:2026-04-12 -->
tomevault-io