decomplect

Analyze code changes for complexity, coupling, and separation concerns.

76|8|Updated Oct 21, 2025

Search Tags:#architecture #coupling #code-review #simplicity #rich-hickey #functional-core

Ready to run

npx skills add https://github.com/shanev/skills --skill decomplect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decomplect
Source: https://github.com/shanev/skills/tree/main/decomplect
Command: npx skills add https://github.com/shanev/skills --skill decomplect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill evaluates code architecture against Rich Hickey's simplicity principles, Gary Bernhardt's FCIS pattern, and classical coupling theory.

Core Features & Use Cases

Multi-Pillar Analysis: Runs three specialized analyzers in parallel for comprehensive assessment.
Design Quality Assessment: Identifies complected concerns, mixed I/O/logic, and poor modularity.
Use Case: When reviewing a pull request with significant architectural changes, use this Skill to ensure the design follows proven simplicity patterns.

Quick Start

Ask Claude to analyze your code changes for architectural quality using the decomplect skill.

Frequently Asked Questions about decomplect

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

FAQPage Schema

How do I evaluate code architecture for simplicity and coupling issues?▼

Architectural code analysis evaluates design quality by identifying complected concerns, mixed logic and I/O, and poor modularity against proven simplicity principles. This Skill analyzes TypeScript, Go, and Rust code changes to measure how well they follow functional-core separation and reduce coupling.

Can I use architectural analysis on pull requests and git diffs?▼

Yes. This Skill applies architectural analysis directly to git diffs, pull requests, and commits in TypeScript, Go, and Rust. It delivers structured assessments with pillar scores, design findings, and refactoring recommendations in a single pass.

What does decomplection mean in code review?▼

Decomplection is the practice of decomposing tangled concerns in code to improve design clarity. It applies Rich Hickey's simplicity principles and Gary Bernhardt's functional-core/imperative-shell pattern to identify where logic, I/O, and state management are unnecessarily mixed.

How do I know if my code changes follow functional-core separation?▼

This Skill runs multi-pillar analysis on your code changes to assess simplicity, functional-core/imperative-shell separation, and coupling. It flags mixed concerns and delivers refactoring recommendations so you can strengthen the boundary between pure logic and side effects.

What languages and change types does architectural analysis support?▼

Architectural analysis works on TypeScript, Go, and Rust code. It processes git diffs, pull requests, and individual commits to evaluate design quality and coupling across these languages.

Why should I review architecture during code review instead of later?▼

Catching architectural issues early—mixed concerns, tight coupling, unclear boundaries—prevents compounding design debt. This Skill identifies these patterns at pull request time so refactoring recommendations can be applied before code merges.