← ClaudeAtlas

gitfx-ownerslisted

Reports who owns which code and what happens if they leave: author share per file and top-level directory from surviving lines (git blame) or commits, bus factor, and files whose main owner has not committed for months (knowledge at risk). Merges aliases through .mailmap and email domains and leaves bots out. Use when the user says "what is our bus factor", "who knows this code", "knowledge at risk", "who owns this module", "what do we lose if she leaves", or "who should review changes to this directory".
vivekbhange-hub/git-forensics-skill · ★ 0 · Code & Development · score 75
Install: claude install-skill vivekbhange-hub/git-forensics-skill
# gitfx-owners: where knowledge is concentrated A file written by one person who has left is a risk you can measure. `owners.py` blames the most changed files, shares the surviving lines out by author, and lists files whose main owner has been silent for `--inactive-days`. It measures commits, not skill, and it is not a performance tool. ## Inputs - A path inside a git repository (default: the current folder). A shallow clone gives wrong owners; check `git rev-parse --is-shallow-repository`. - Optional: `--since "24 months ago"` for commit shares, `--as-of 2026-11-01` to fix "today", `--inactive-days 180`, `--fast` (no blame), `--file PATH` (blame exactly these files), `--merge-email-domain corp.example.com`, `--exclude-author REGEX`. - Commands below say `python3`; on Windows use `python` (or `py -3`). `git` must be on the PATH. ## Outputs - `gitfx/owners.md` (or the path the user prefers): repository bus factor, directory table, most-changed files with owner and share, and the knowledge-at-risk table. - In chat: the bus factor with its basis, the 3 to 5 knowledge-at-risk files, and a suggested handover action for each (pairing, docs, a review rota), phrased about files and teams. ## Steps 1. **Confirm permission.** Ask once whether the user owns or is authorized to analyse this repository. This report contains names and email-derived identities of colleagues; if the repo is not the user's to analyse, stop. 2. **Check the identity hygiene** before run