analyze-git-churn SKILL.md skillA
analyze-git-churn from tomzx/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tomzx/agents/analyze-git-churn@git:20261007.b35fc4bPins git:20261007.b35fc4b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tomzx/agents
- Path
skills/analyze-git-churn/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261007.b35fc4b, committed Oct 7, 2026
- First version recorded
- May 29, 2026
- Size
- 7,170 bytes
- Repository stars
- 12
- License
- MIT
Analyze git history to identify high-churn files and suggest targeted improvements such as refactoring, test coverage, dead code removal, or library replacements.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
TODAY=!`date +%Y-%m-%d` # Git Churn Analysis Analyzes the git commit history over a chosen period to find the files that changed most frequently, then inspects each high-churn file and produces concrete, prioritized improvement suggestions. ## Prerequisites - `git` repository with commit history - Working directory is the root of the repository (or a subdirectory of it) - Optional: `$1` — period to analyze: `day`, `week`, or `month` (defaults to `week`) ## Period Mapping | Argument | `--since` value | |----------|----------------| | `day` | `1 day ago` | | `week` | `1 week ago` | | `month` | `1 month ago` | If `$1` is not provided, default to `week`. ## Steps ### 1. Determine the Analysis Window Map `$1` → a `git log --since` value using the table above. ### 2. Collect Churn Data Run the following to count how many commits touched each file in the window: ``` git log --since="<period>" --name-only --pretty=format: | sort | uniq -c | sort -rn | head -30 ``` Also capture per-file insertion/deletion totals to measure change volume: ``` …
Read the whole file at its exact version.
How to install
mdr add tomzx/agents/analyze-git-churn@sha256:072810083890c6a8The line at the top of this page pins the label git:20261007.b35fc4b, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2lzyvvyei76slqkb)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between May 29, 2026 and Oct 7, 2026, about one every 44 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.b35fc4b latest | 2026-10-07 | b35fc4b | 7,170 B | A | view · diff |
| git:20261004.00bb0c5 | 2026-10-04 | 00bb0c5 | 7,170 B | A | view · diff |
| git:20260601.bca31c7 | 2026-06-01 | bca31c7 | 7,198 B | A | view · diff |
| git:20260529.3f79c00 | 2026-05-29 | 3f79c00 | 7,201 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7170 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tomzx/agents · 12 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2lzyvvyei76slqkb GET https://markdownregistry.com/api/v1/resolve?ref=tomzx/agents/analyze-git-churn GET https://markdownregistry.com/api/v1/blob/072810083890c6a8b100645578613d7613d497d6844c13161dfb1d28e5be6ddb
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.