analysis-dimensions

Detect duplicate code blocks and map architectural structure across a codebase.

11|Updated Nov 5, 2025

Search Tags:#architecture #analysis #metrics #quality #dimensions

Ready to run

npx skills add https://github.com/d-o-hub/rust-self-learning-memory --skill analysis-dimensions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analysis-dimensions
Source: https://github.com/d-o-hub/rust-self-learning-memory/tree/main/.claude/skills/codebase-consolidation/analysis-dimensions.md
Command: npx skills add https://github.com/d-o-hub/rust-self-learning-memory --skill analysis-dimensions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This file defines the analysis dimensions used by codebase consolidation, enabling systematic evaluation of code quality and architecture.

Core Features & Use Cases

Dimension criteria: structure, duplication, complexity, tests, docs, security.
Assessment guidance: how to measure and report findings.

Quick Start

Use the analysis checklist to generate a structured quality report.

Frequently Asked Questions about analysis-dimensions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I identify duplicate code blocks across my codebase?▼

Code duplication detection systematically scans your codebase to find redundant or similar code blocks, consolidating them to reduce maintenance overhead. This analysis produces a structured map of duplication patterns across your architecture, helping you prioritize refactoring and understand technical debt.

What dimensions should I use to evaluate code quality and architecture?▼

Quality assessment uses six core dimensions: structure, duplication, complexity, tests, documentation, and security. Each dimension provides measurable criteria for evaluating your codebase, enabling systematic reporting from architect, developer, and product perspectives.

How can I generate an architecture map and identify refactoring opportunities?▼

Apply structured analysis across your codebase to produce architecture maps that reveal structural patterns, consolidation opportunities, and technical-debt areas. This generates actionable refactoring roadmaps usable in planning, onboarding, modernization, and pre-release audits.

Can I use this analysis for legacy system modernization?▼

Yes. The analysis framework supports legacy modernization workflows by consolidating duplicate code, mapping architectural structure, quantifying technical debt, and generating documentation and roadmaps tailored for modernization planning and stakeholder communication.

What outputs does the analysis produce?▼

The analysis delivers multi-format outputs including executive summaries for leadership, detailed architecture documentation for engineers, technical-debt prioritization reports, and modernization roadmaps—all derived from the same underlying quality metrics.

When should I run codebase analysis in my development workflow?▼

Run analysis during codebase discovery, refactoring planning, documentation generation, team onboarding, legacy modernization initiatives, and pre-release audits to catch duplication, understand architecture, and quantify technical debt before it compounds.