hidden-coupling-vault-auth

Flags hidden co-change coupling between vault member routes and auth test files.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/ZaxbyHub/ragappv3 --skill hidden-coupling-vault-auth-zaxbyhub
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hidden-coupling-vault-auth
Source: https://github.com/ZaxbyHub/ragappv3/tree/main/.opencode/skills/generated/hidden-coupling-vault-auth
Command: npx skills add https://github.com/ZaxbyHub/ragappv3 --skill hidden-coupling-vault-auth-zaxbyhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Files that change together but share no import relationship reveal hidden architectural coupling that developers often miss, causing incomplete changes and broken tests. This Skill captures three recorded lessons showing that backend/app/api/routes/vault_members.py co-changes with three test files at NPMI=1.000. ## Core Features & Use Cases - Hidden Coupling Awareness: Records that vault_members.py co-changes with test_auth_routes.py, test_vault_group_access_routes.py, and test_vault_members_routes.py despite having no import relationship. - Change Guidance: Instructs that modifications to the vault members route likely require corresponding updates to all three coupled test files. - Use Case: When editing backend/app/api/routes/vault_members.py, apply this Skill to remember to update the three coupled test files in the same change, avoiding CI failures from stale tests. ## Quick Start Apply this skill whenever modifying backend/app/api/routes/vault_members.py and update the three coupled test files in the same commit.

Frequently Asked Questions about hidden-coupling-vault-auth

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

FAQPage Schema
What is hidden coupling between source files?▼

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

Which files are coupled with vault_members.py?▼

Three test files co-change with backend/app/api/routes/vault_members.py at NPMI=1.000: test_auth_routes.py, test_vault_group_access_routes.py, and test_vault_members_routes.py, all under backend/tests/.

How do I apply this skill when editing vault routes?▼

When modifying backend/app/api/routes/vault_members.py, review and update the three coupled test files in the same change. Reviewers should verify each required update appears in the diff.

What does NPMI=1.000 mean for co-change detection?▼

NPMI (Normalized Pointwise Mutual Information) of 1.000 indicates the files always change together in the commit history. It is the strongest possible co-change signal, even without a direct code dependency.

When should this coupling lesson not apply?▼

The lesson only applies to changes touching vault member route logic or its authorization behavior. Unrelated refactors in other backend modules do not require updating these specific test files.