Ranks git repository files and directories by change frequency, recency, and author spread.
npx skills add https://github.com/vinzenz/workflows --skill churn-vinzenz
Please help me install this Agent Skill. Skill: churn Source: https://github.com/vinzenz/workflows/tree/main/.agents/skills/churn Command: npx skills add https://github.com/vinzenz/workflows --skill churn-vinzenz
git log --numstat pass into a ranked hotspot list, replacing O(files) per-file log inspection with a single scan. ## Core Features & Use Cases - Ranked hotspot lists: churn files and churn dirs rank paths by a transparent score combining commit count, recency multiplier, and distinct author count. - Single-file history: churn file <path> follows renames through all history to tell one file's complete story. - Noise filtering: Lockfiles, dist/, node_modules/, and vendored paths are excluded by default so generated code never dominates the rankings. - Use Case: An agent starting work in a new repo runs churn dirs --depth 1 to identify the project's center of gravity before editing anything. ## Quick Start Use the churn skill to show me which files and directories in this repository change most often and were touched most recently.High-intent search queries and answers about installing and using this skill.
Run `churn files` to get a ranked table of paths with commits, authors, added/deleted lines, and last-change recency. Use `--since` to widen or narrow the window, for example `churn files --since 6m`.
Run `churn dirs` to roll the same change-frequency signal up per directory, which is often more useful than per-file rankings. Adjust grouping with `--depth`, for example `churn dirs --depth 1` for a top-level view.
Yes, but a shallow clone adds a `history:` line warning that counts are a lower bound, not the complete picture. Results are never silently treated as complete history.
Generated and vendored paths like package-lock.json, dist/, node_modules/, and *.min.* are excluded by default because they are regenerated noise, not real hotspots. Pass `--include-generated` to see them anyway.
Score equals commits times a recency multiplier plus authors times three. The multiplier is x5 for changes within 7 days, x3 within 30, x2 within 90, x1 within a year, and x0 beyond that, and every row prints the exact inputs.
psw7205Diagnoses codebase health by cross-analyzing Git history churn, bug clusters, and contributor activity.
mattnowdevIdentify refactoring-relevant code smells in pull request diffs.
udecodeAnalyze Git history to trace code evolution and identify contributors.
LilwenzRefactor complex Python code into maintainable implementations with validation.