code-arch-optimizer

Name: code-arch-optimizer
Availability: InStock
Author: haomingz

Analyze module boundaries and coupling to generate RFC-style refactor plans.

12|2|Updated Apr 21, 2026

Search Tags:#modularity #refactor #RFC #analyze #code-architecture #github-issues #architecture-evaluation

Ready to run

npx skills add https://github.com/haomingz/kimi-skills --skill code-arch-optimizer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-arch-optimizer
Source: https://github.com/haomingz/kimi-skills/tree/main/skills/code-arch-optimizer
Command: npx skills add https://github.com/haomingz/kimi-skills --skill code-arch-optimizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyses codebases to surface architectural friction and provides concrete, RFC-style deep-modularization strategies to enable safer, more testable evolution.

Core Features & Use Cases

Friction detection: Identify tight couplings, vague interfaces, and brittle module boundaries across the codebase.
RFC-driven proposals: Generate multiple structured refactor options with trade-offs, dependencies, and testing considerations.
Guided execution plan: Produce actionable steps and checkpoints suitable for GitHub Issues to drive a project-wide refactor.

Quick Start

Run a guided assessment by prompting for a deep modularization plan.

Frequently Asked Questions about code-arch-optimizer

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

FAQPage Schema

How do I identify code architecture friction for a deep refactor?▼

Code architecture friction is identified by analyzing module boundaries, interfaces, and coupling to detect tight dependencies and brittle structures. This analysis surfaces vague interfaces, enabling targeted deep-module refactoring strategies for safer codebase evolution.

What is the best way to generate RFC-style proposals for code refactoring?▼

RFC-style refactor proposals are generated by evaluating module boundaries and producing structured options with concrete trade-offs. This process yields multiple scenario-based refactoring strategies, detailing dependencies, risks, and testing considerations for guided execution.

How do I create a guided execution plan for a modularization refactor?▼

A guided execution plan is created by translating architecture evaluation results into actionable steps and checkpoints. This output formats deep-module refactor proposals into structured tasks suitable for GitHub Issues, driving project-wide modularization.

Can I use architecture evaluation to plan refactors for tightly coupled modules?▼

Architecture evaluation analyzes tight couplings and vague module boundaries to propose deep-module refactor plans. It generates structured, RFC-style options with specific trade-offs and testing considerations, ensuring safe modularization of coupled codebases.

When should I not use deep-module refactor strategies?▼

Deep-module refactor strategies require careful risk assessment when architecture friction involves complex dependencies. Limitations arise when vague interfaces lack clear testing checkpoints, making RFC-driven proposals harder to execute without introducing regression risks.