From janmarkuslanger-engineering
Analyzes a module or codebase for coupling quality. Distinguishes intentional from accidental coupling, identifies problematic dependencies, and recommends concrete improvements.
How this skill is triggered — by the user, by Claude, or both
Slash command
/janmarkuslanger-engineering:coupling-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When this skill is activated, analyze the coupling structure of a specified module, feature, or the entire codebase and produce a `docs/reviews/COUPLING_REVIEW.md` report.
When this skill is activated, analyze the coupling structure of a specified module, feature, or the entire codebase and produce a docs/reviews/COUPLING_REVIEW.md report.
Before starting the review, ask the engineer the following questions. Skip any already clearly answered in the conversation. Wait for the answers before proceeding.
Write a file called docs/reviews/COUPLING_REVIEW.md (create the docs/reviews/ folder if it does not exist) with the following sections:
What was analyzed (files, modules, feature boundaries).
A Mermaid diagram of all identified dependencies within the analyzed scope:
graph TD
A[ModuleA] -->|imports| B[ModuleB]
A -->|calls| C[Service]
B -->|reads| D[(Database)]
Use different arrow labels to indicate coupling type: imports, calls, extends, reads, writes, emits, listens.
A table of all significant couplings found:
| From | To | Type | Intentional? | Strength | Assessment |
|---|---|---|---|---|---|
| OrderService | PaymentGateway | direct call | yes | high | OK — stable external contract |
| OrderService | UserRepository | direct import | no | high | Problem — crosses bounded contexts |
Strength: low (can change independently) | medium | high (change in one forces change in other)
Assessment: OK | Tolerable | Problem | Critical
For each Problem or Critical coupling, a dedicated entry:
Issue: {Short Name}
List any circular dependencies found. These are always problems. Include the full cycle and a recommended break point.
| Category | Count |
|---|---|
| Total couplings analyzed | N |
| Intentional & healthy | N |
| Tolerable (document but accept) | N |
| Problems (should fix) | N |
| Critical (fix before next release) | N |
One paragraph of overall assessment: is the coupling structure sound, or does it indicate deeper design problems?
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub janmarkuslanger/skills --plugin janmarkuslanger-engineering