general-decomposition

Name: general-decomposition
Availability: InStock
Author: buchananwill

Review codebases to identify decomposition opportunities and extract responsibility groups into modular units.

2|Updated Mar 17, 2026

Search Tags:#architecture #refactoring #decomposition #code-review #modularization #nesting

Ready to run

npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill general-decomposition

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: general-decomposition
Source: https://github.com/buchananwill/ue-claude-scaffold/tree/main/skills/general-decomposition
Command: npx skills add https://github.com/buchananwill/ue-claude-scaffold --skill general-decomposition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review codebases to identify bloated structures, excessive nesting, DRY violations, and opportunities for clean decomposition into smaller, cohesive units.

Core Features & Use Cases

Identifies responsibility groups such as class/struct definitions, clusters of free functions, self-contained algorithms, and blocks of type definitions.
Flags DRY violations and recommends extraction into named helpers or modules with minimal disruption to behavior.
Provides decomposition execution rules and guidelines to preserve interfaces, maintain tests, and document rationale.

Quick Start

Run a codebase review to identify decomposition opportunities and extract responsibility groups into focused modules without changing behavior.

Frequently Asked Questions about general-decomposition

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

FAQPage Schema

How do I identify code bloat and deep nesting for refactoring?▼

Refactoring a legacy codebase involves reviewing its structure to extract responsibility groups into modular units. It provides rules-based guidance to preserve interfaces and document rationale while decomposing bloated logic into cohesive, maintainable modules.

What is the best way to decompose a large legacy codebase into modules?▼

Decomposing a large legacy codebase requires extracting responsibility groups such as class definitions and self-contained algorithms into focused modules. Rules-based guidance ensures interfaces are preserved, tests are maintained, and rationale is documented throughout the modularization process.

Can I use this decomposition approach across different programming languages?▼

Yes, this decomposition approach is applicable to large or legacy codebases across multiple languages. It detects bloat, excessive nesting, and DRY violations regardless of the specific programming language used in your project.

How do you preserve interfaces when extracting responsibilities during a code review?▼

Preserving interfaces during code review involves following decomposition execution rules that maintain tests and document rationale. It ensures responsibility groups are extracted into named helpers or modules with minimal disruption to existing behavior.

When should I modularize code to fix DRY violations?▼

You should modularize code to fix DRY violations when a review identifies repeated logic that can be extracted into named helpers. This decomposition approach targets clusters of free functions and type definitions to reduce bloat and improve maintainability.