refactor-architecture

Analyze codebase modules and coupling to produce a refactor-architecture proposal.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/JonnyCBB/claude-code-config --skill refactor-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactor-architecture
Source: https://github.com/JonnyCBB/claude-code-config/tree/main/plugins/eng-utils/skills/refactor-architecture
Command: npx skills add https://github.com/JonnyCBB/claude-code-config --skill refactor-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify architectural friction in a codebase and produce a formal refactor-architecture proposal.

Core Features & Use Cases

  • Analyze codebase to identify scattered concepts, shallow modules, and tight coupling.
  • Design multiple interface options and generate a proposal document with old/new architecture diagrams and pros/cons.
  • Provide a proposal-only output with no code changes, ready for /create-plan-tdd integration.

Quick Start

Provide a refactor-architecture proposal for the given scope path

Frequently Asked Questions about refactor-architecture

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

FAQPage Schema
How do I create a formal proposal to refactor codebase architecture and reduce tight coupling?

This Skill analyzes a given scope path to identify scattered concepts and tight coupling, then generates a formal refactor proposal document with architecture diagrams and interface options for review.

What is the best way to analyze architectural friction in a module before writing code?

Analyzing architectural friction involves reading dependency categories and friction patterns across modules to detect shallow structures, then designing interface options to formalize the refactor scope before any code changes occur.

How do I generate architecture diagrams for a proposed codebase refactor?

Generating architecture diagrams requires running this Skill on a target scope path; it produces a Phase 4 proposal document containing old and new architecture diagrams alongside pros and cons.

Does this architecture refactor proposal output modify my existing codebase?

No, the architecture refactor output is proposal-only with no code changes. It saves a formal proposal document under the shared refactor-proposals directory, ready for subsequent integration with a TDD planning workflow.

How do I structure an interface design proposal for a tightly coupled codebase?

Structuring an interface design proposal requires analyzing module coupling and interfaces within a given scope path, then designing multiple interface options using a proposal template to document the architectural changes.

When should I not use an automated architecture refactor proposal?

You should not use an automated architecture refactor proposal when you need immediate code changes rather than a formal review document, as the output is strictly a proposal with diagrams and does not modify the codebase.