architectural-analysis

Analyze codebases to detect dead code, duplication, anti-patterns, and type issues.

Updated May 28, 2026
One-click install
npx skills add https://github.com/haryelramalho/skills --skill architectural-analysis-haryelramalho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architectural-analysis
Source: https://github.com/haryelramalho/skills/tree/main/skills/curated/architectural-analysis
Command: npx skills add https://github.com/haryelramalho/skills --skill architectural-analysis-haryelramalho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a deep architectural audit to uncover dead code, duplicated functionality, type confusion, code smells, and structural anti-patterns that make a codebase harder to maintain.

Core Features & Use Cases

  • Dead Code Detection: Identifies unused files, exports, private methods, and variables that can be removed safely.
  • Duplication and Anti-Pattern Analysis: Spots repeated logic, god objects, circular dependencies, tight coupling, and layer violations.
  • Type and Code Smell Review: Flags risky type usage, complex conditionals, magic numbers, poor naming, and commented-out code.
  • Use Case: Run it when you need a systematic health check of a repository before refactoring, cleanup, or a major release.

Quick Start

Ask the Skill to analyze the repository architecture and produce a complete report of dead code, duplication, anti-patterns, type issues, and cleanup opportunities.

Frequently Asked Questions about architectural-analysis

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

FAQPage Schema
How do I find dead code and unused exports in my repository?

Dead code detection identifies unused files, exports, private methods, and variables by performing systematic file-by-file inspection and import tracing across the repository. It quantifies findings to guide safe code removal during refactoring.

What is the best way to detect circular dependencies and architectural anti-patterns?

Architectural analysis spots structural anti-patterns like circular dependencies, god objects, tight coupling, and layer violations by inspecting source files and tracing imports. It produces a quantified report of structural flaws for maintainability assessments.

How do I check for code smells and type confusion before a major release?

Type and code smell review flags risky type usage, complex conditionals, magic numbers, and commented-out code during a repository-wide audit. It systematically inspects files to quantify code health issues before refactoring or release.

Can I use this architectural analysis for repository-wide refactoring planning?

Yes, architectural analysis applies directly to repository-wide audits, refactoring planning, and code health reviews. It systematically inspects source files, verifies duplication, detects type issues, and quantifies cleanup opportunities for maintainability assessments.

Does dead code detection work without external dependencies or components?

Dead code detection operates with no external dependencies or components, relying solely on systematic file-by-file inspection and import tracing across source files. It independently identifies unused exports and variables for maintainability assessments.