gitfx-couplinglisted
Install: claude install-skill vivekbhange-hub/git-forensics-skill
# gitfx-coupling: what really depends on what
Import graphs show the dependencies you declared. Version control shows the ones you have:
files that are edited in the same commit again and again. `coupling.py` counts those pairs from
`git log` and flags the ones with no visible link between them.
## Inputs
- A path inside a git repository (default: the current folder).
- Optional: a window (`--since "12 months ago"`), a sub-tree (`--path src`), thresholds
`--min-shared` (default 3) and `--min-confidence` (default 0.5), `--max-files` (default 30).
- Commands below say `python3`; on Windows use `python` (or `py -3`). `git` must be on the PATH.
## Outputs
- `gitfx/coupling.md` (or the path the user prefers): pairs with shared commits, support,
confidence both ways, cross-module and reference flags, and clusters.
- In chat: the 3 to 5 pairs that matter, the likely cause of each, and one concrete change each.
## Steps
1. **Confirm permission.** Ask once whether the user owns or is authorized to analyse this
repository. If not, stop.
2. **Run the script** over a recent window:
```
python3 "${CLAUDE_SKILL_DIR}/coupling.py" . --since "12 months ago" --top 25 -o gitfx/coupling.md
python3 "${CLAUDE_SKILL_DIR}/coupling.py" . --since "12 months ago" --hidden-only --top 10
```
The second command keeps only cross-module pairs with no visible reference, test pairs
excluded. Commits that touch more than `--max-files` files are skipped as bulk edits.
3. **Read