skills.rest
ZaxbyHub
ZaxbyHubOFFICIAL
Explore all skills by this author →
GitHub

hidden-coupling-cochange

Detects hidden file coupling from co-change patterns lacking import relationships.

Updated Mar 30, 2026
Search Tags:#architecture#code review#refactoring#git history#hidden coupling#co-change analysis#npmi
One-click install
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill hidden-coupling-cochange-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hidden-coupling-cochange
Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.opencode/skills/generated/hidden-coupling-cochange
Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill hidden-coupling-cochange-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Files that change together in version control but share no import relationship create hidden architectural coupling, causing missed updates and regressions when only one file is modified. ## Core Features & Use Cases - Co-Change Detection: Surfaces file pairs with high NPMI co-change scores (0.944-1.000) that lack direct import dependencies. - Architecture Lessons: Records ten documented coupling cases spanning backend routes, test suites, frontend components, and PowerShell scripts. - Delegation Support: Provides a delegation template and reviewer checklist so coupled files are verified together in diffs. - Use Case: When modifying backend/app/api/routes/wiki.py, this Skill reminds you to also review wiki_compiler.py and WikiJobsPanel.tsx, which historically change alongside it. ## Quick Start Apply this skill when editing any of the listed coupled files so the paired file is reviewed and updated in the same change.

Frequently Asked Questions about hidden-coupling-cochange

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

FAQPage Schema
What is hidden coupling in a codebase?▼

Hidden coupling occurs when two files frequently change together in commits but have no import or dependency relationship. It signals a shared architectural concern, meaning edits to one file likely require matching edits to the other.

How do I detect files that co-change without imports?▼

Analyze git history with NPMI (Normalized Pointwise Mutual Information) scoring to find file pairs that commit together frequently, then filter out pairs with direct import relationships. Pairs scoring near 1.0 indicate strong hidden coupling.

What does an NPMI score of 1.0 mean for file coupling?▼

An NPMI score of 1.0 means the two files always change together in the commit history. When no import relationship exists between them, this perfect co-change indicates an implicit dependency that developers must maintain manually.

When should I apply co-change lessons during code review?▼

Apply them whenever a diff touches one file of a known coupled pair, such as a route file and its test suite. The reviewer checklist requires verifying that the paired file was also updated or consciously left unchanged.

What are the limitations of co-change coupling analysis?▼

Co-change analysis reflects historical commit patterns, not true semantic dependencies, so it can produce false positives from coincidental edits. This skill also carries a low confidence score of 0.37, so findings should be validated before restructuring code.

Related Skills

Explore More Software Engineering Skills→
Intense-VisionsIntense-Visions
18

harness-hotspot-detector

Analyze Git history and churn data to rank structural risk hotspots.

Official
Advanced
Codeplain-aiCodeplain-ai

consolidate-concepts

Consolidate concept definitions from multiple modules into one shared import module.

Official
Advanced
messebmesseb

dry

Identify duplicated knowledge in codebases and suggest DRY refactoring strategies.

Community
Intermediate
agnaldo4jagnaldo4j
1

circular-dependency-control

Detect and classify circular dependencies across Kotlin class, package, and Gradle module boundaries.

Community
Advanced