architectural-analysis

Audit repositories for dead code, duplication, anti-patterns, and code smells.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you audit a codebase to locate dead code, duplicated functionality, architectural anti-patterns, type safety problems, and code smells so you can improve maintainability without guessing.

Core Features & Use Cases

  • Dead Code Detection: Identifies unused exports, never-called functions/classes, and internal unused code by mapping exports and checking real usage.
  • Duplication Discovery: Finds exact and similar duplicated logic (including type duplication) so teams can consolidate implementations and reduce maintenance risk.
  • Architecture & Quality Review: Flags architectural anti-patterns (god objects, circular dependencies, layer violations), type issues (any/unknown/assertions), and code smells (long methods, magic numbers, commented-out code).
  • Structured Audit Output: Produces a timestamped report with quantified impact and actionable recommendations, including confidence levels.

Quick Start

Ask the AI to run an architectural analysis of your repository and generate a full report including dead code, duplication groups, architectural anti-patterns, type issues, code smells, and a cleanup impact estimate.

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 duplicated functionality in a TypeScript repository?

An architectural analysis finds dead code and duplication in a TypeScript repository by mapping exports to real usage and categorizing similar logic. It identifies unused exports, never-called functions, and duplicated implementations to reduce maintenance risk.

What is the best way to detect architectural anti-patterns and code smells for refactoring planning?

The best way to detect architectural anti-patterns and code smells for refactoring planning is a comprehensive code health review. It flags god objects, circular dependencies, layer violations, long methods, and magic numbers to improve maintainability without guessing.

How do I generate a maintainability audit report with confidence and impact estimates?

You generate a maintainability audit report by running a systematic architectural analysis that produces a structured, timestamped output. This report quantifies cleanup impact and provides actionable recommendations alongside confidence levels for each detected issue.

Can I use architectural analysis for legacy code cleanup and evaluating code health before changes?

Yes, architectural analysis applies directly to legacy cleanups and evaluating code health before making changes. It systematically discovers files, verifies export-to-usage, and detects type confusion and anti-patterns to ensure safe refactoring.

Does architectural analysis detect type safety problems like any and unknown assertions?

Architectural analysis detects type safety problems by scanning for any, unknown, and type assertions. Identifying these type issues alongside code smells helps teams consolidate implementations and improve overall TypeScript quality.