keeping-git-repos-clean SKILL.md skillF
keeping-git-repos-clean from kajisho5/ffmpeg-skill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kajisho5/ffmpeg-skill/keeping-git-repos-clean@git:20260906.24c1610Pins git:20260906.24c1610 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- F, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kajisho5/ffmpeg-skill
- Path
.claude/skills/git-hygiene/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260906.24c1610, committed Sep 6, 2026
- Size
- 8,508 bytes
- Repository stars
- 2,026
- License
- MIT
Prevents, detects, and remediates files that should never be committed — secrets (.env, API tokens, hardcoded credentials) and dev artifacts (build output, scratch databases, editor/OS files). Covers .gitignore (and why it does not untrack), git rm --cached, auditing tracked files, history scrubbing, and credential rotation. Use when a repo has committed secrets or junk, when setting up a new repo's ignore rules, or when reviewing what a repo actually tracks.
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
# Keeping Git Repos Clean Two classes of files keep ending up in repos: **secrets** and **dev artifacts**. Both are cheap to prevent and expensive to clean up after the fact, because git history is forever and public repos publish everything. ## The one rule everyone forgets **`.gitignore` does NOT untrack files that are already committed.** Adding a path to `.gitignore` only prevents *future untracked* files from being staged. A file git is already tracking keeps getting committed regardless. This bites repeatedly: a `.env` is listed in `.gitignore` but was committed before the rule existed, so it keeps shipping. To actually stop tracking a file while keeping your local copy: ```bash git rm --cached path/to/file # untrack, leave working-tree copy in place git rm -r --cached some/dir/ # for a directory echo "path/to/file" >> .gitignore # then ignore it so it doesn't come back git commit -m "Stop tracking <file>; add to .gitignore" ``` `--cached` is the important flag — plain `git rm` deletes the working copy too. ## Audit what a repo actually tracks Don't trust `.gitignore` to tell you what's clean — read the index directly: ```bash …
Read the whole file at its exact version.
How to install
mdr add kajisho5/ffmpeg-skill/keeping-git-repos-clean@sha256:c6e74fcf81919674The line at the top of this page pins the label git:20260906.24c1610, 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_kczt4tuvxb2ukjrc)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 6, 2026.
Audit of the latest version
- FAIL, critical: No instruction to send local credentials anywhere (matched: forward** (`git rm --cached` + `.gitignore` + `.env)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (8508 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 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
kajisho5/ffmpeg-skill · 2,026 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kczt4tuvxb2ukjrc GET https://markdownregistry.com/api/v1/resolve?ref=kajisho5/ffmpeg-skill/keeping-git-repos-clean GET https://markdownregistry.com/api/v1/blob/c6e74fcf819196746d9385b3f310987aaa10816e4528310c2b1b694590dbab9a
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.