improve-codebase-architecture

Identify refactor candidates in TypeScript codebases using architectural analysis and coding standards.

Updated May 7, 2026
One-click install
npx skills add https://github.com/Matthieusz/skills --skill improve-codebase-architecture-matthieusz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-codebase-architecture
Source: https://github.com/Matthieusz/skills/tree/main/improve-codebase-architecture
Command: npx skills add https://github.com/Matthieusz/skills --skill improve-codebase-architecture-matthieusz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of identifying refactor candidates within a codebase based on architectural evidence and coding standards, eliminating manual analysis and enhancing efficiency.

Core Features & Use Cases

  • Architecture Scan: Conducts an in-depth scan of a codebase to find potential refactor candidates.
  • Evidence-Based Refactoring: Identifies refactor candidates that can improve code quality based on evidence and coding standards.
  • Use Case: Ideal for developers or architects looking to enhance code quality and structure without extensive manual analysis.

Quick Start

Run the improve-codebase-architecture skill within your desired codebase to automatically identify refactor candidates.

Frequently Asked Questions about improve-codebase-architecture

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

FAQPage Schema
How do I identify TypeScript refactor candidates automatically?

You can identify TypeScript refactor candidates automatically by running an architecture scan that analyzes coding standards and architectural evidence across repository, directory, module, or file set scopes to pinpoint areas needing structural improvement.

What is evidence-based refactoring for code architecture?

Evidence-based refactoring uses architectural analysis and coding standards to identify code areas needing improvement. It evaluates evidence halos across repository, directory, feature, module, or file set scopes to find concrete refactor candidates rather than guessing.

Can I run a code architecture scan on a specific directory or feature module?

Yes, code architecture scans support repository, directory, feature, module, file set, or concern scopes. You can target specific directories or feature modules to narrow the architectural analysis and find refactor candidates within those boundaries.

What's the best way to find code refactoring targets without manual analysis?

This approach automates architectural analysis and applies coding standards with evidence halos to generate concrete refactor candidates. This eliminates manual codebase review and provides structured, evidence-backed targets for improving code quality and structural integrity.

Do I need to define coding standards before scanning for architectural refactor candidates?

Coding standards are incorporated into the architectural analysis to identify refactor candidates based on evidence. Defining or providing these standards ensures the scan produces evidence-backed results aligned with your specific code quality and structural requirements.

Does this approach work for large TypeScript codebases?

The scan considers evidence halos and coding standards across various scopes to pinpoint refactor candidates. This method is ideal for large TypeScript codebases where developers or architects need to enhance code structure and quality without performing extensive manual analysis.