code-review

Analyze code coupling strength and detect connascence issues across modules.

1|Updated Jan 3, 2022

Search Tags:#architecture #quality-assurance #code-review #software-design #coupling-strength #connascence

Ready to run

npx skills add https://github.com/daikichiba9511/dotfiles --skill code-review-daikichiba9511

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/daikichiba9511/dotfiles/tree/main/private_dot_codex/skills/code-review
Command: npx skills add https://github.com/daikichiba9511/dotfiles --skill code-review-daikichiba9511

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams assess code quality by measuring coupling strength and detecting connascence issues, providing actionable feedback to improve maintainability and design.

Core Features & Use Cases

Evaluate data, stamp, control, common, and content coupling between modules to surface design weaknesses.
Detect connascence types (name, type, meaning, position, algorithm) and guide refactoring.
Use in code reviews, architecture assessments, and pre-refactor planning to reduce risk and improve decoupling.
Real-world example: evaluate a set of interconnected services to pinpoint where changes may ripple across modules.

Quick Start

Ask the tool to review the provided codebase focusing on coupling strength and connascence and return actionable feedback.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I measure coupling strength and connascence issues during a code review?▼

Yes, you can review coupling strength and connascence in any programming language. The analysis applies to any codebase where modules and interfaces can be evaluated, allowing you to detect software design weaknesses and plan refactors regardless of the specific technology stack.

What is the best way to identify which modules will cause ripple effects before refactoring?▼

The best way to identify ripple effects before refactoring is to assess connascence types and coupling strength across interconnected modules. Quantifying these dependencies pinpoints exactly where changes may propagate, reducing risk and improving decoupling during architecture audits.

How do I detect control and content coupling weaknesses in my software design?▼

Detect control and content coupling weaknesses by applying evaluation criteria to your interconnected services and modules. Analyzing these specific coupling categories surfaces hidden design flaws and provides targeted improvement feedback to guide your refactoring strategy.

Can I use connascence analysis for pre-refactor planning in an existing architecture?▼

Yes, you can use connascence analysis for pre-refactor planning in an existing architecture. Evaluating coupling strength and connascence types like algorithm and position helps reduce refactoring risk by precisely mapping module dependencies before making changes.

Why does my code review fail to catch maintainability issues across interconnected services?▼

Code reviews often fail to catch maintainability issues when they lack a quantitative evaluation of coupling strength and connascence. Without checking consistent naming, type, and meaning dependencies, hidden design weaknesses and ripple effects across modules remain undetected.