complexity-recognition
Diagnoses what makes code complex and why, using the three-symptom two-root-cause framework. Use when code feels harder to work with than it should but the specific problem is unclear. This skill identifies WHETHER complexity exists and WHERE it comes from. Not for scanning a checklist of known design smells (use red-flags) or evaluating a specific module's depth (use deep-modules).
npx skills add majiayu000/claude-skill-registry --skill complexity-recognition --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Complexity Recognition Review Lens When invoked with $ARGUMENTS, focus the analysis on the specified file or module. Read the target code first, then apply the checks below. > "Complexity is anything related to the structure of a software system that makes it hard to understand and modify the system." — John Ousterhout, _A Philosophy of Software Design_ Complexity is relative to the task: the same codebase can feel simple for one operation and painful for another. The writer of the code is often the worst judge of its complexity. If reviewers find it complex, it is. Diagnose it using three symptoms, two root causes, and the fundamental formula. ## When to Apply - When code feels harder to work with than it should be - When small changes require edits in many places - When developers frequently introduce bugs in unfamiliar code - During "should we refactor this?" discussions ## Core Principles ### The Complexity Formula $$C = \sum_{p}(c_p \times t_p)$$ Each part's complexity weighted by how often developers work with it. - Complexity in frequently-touched code matters most - Encapsulating complexity where it won't be encountered is nearly as valuable as eliminating it > "Complexit
- When to Apply
- Core Principles
- The Complexity Formula
- Three Symptoms
- Two Root Causes
- Hidden Dependencies Are the Worst
- Complexity Is Incremental
- Elimination vs. Encapsulation
- Review Process
What does the complexity-recognition skill do?
Diagnoses what makes code complex and why, using the three-symptom two-root-cause framework. Use when code feels harder to work with than it should but the specific problem is unclear. This skill identifies WHETHER complexity exists and WHERE it comes from. Not for scanning a checklist of known design smells (use red-flags) or evaluating a specific module's depth (use deep-modules).
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill complexity-recognition --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.