agentleFS
Sign inStart free
trac3r00trac3r00/agent-skills/skills/repo-audit/SKILL.md

repo-audit

Skill0 starsChanged 3 months agoMITView on GitHub

Structural health check for a git repository — LICENSE, README, tests, CI config, .gitignore, large tracked files, and stale merged branches (idle beyond a configurable window). Offline, stdlib + git CLI, deterministic. Use when inheriting a repo, before open-sourcing, or as a periodic hygiene gate across many repos.

23 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use handoff.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

Create a free account to mount
Files
SKILL.md

Repo Audit

"Is this thing maintained?" in one deterministic pass.

Commands

python3 scripts/repo_audit.py .                 # this repo
python3 scripts/repo_audit.py ~/src --json      # any repo
python3 scripts/repo_audit.py . --stale-days 60
python3 scripts/repo_audit.py . --fail-on license,tests
for d in ~/src/*/; do python3 scripts/repo_audit.py "$d" --json; done

Checks

CheckFail when
licenseno LICENSE file
readmeno README
testsno test files detected
cino CI config (GitHub Actions, GitLab CI, CircleCI)
gitignoremissing (untracked junk risk)
large_filestracked files over 5MB (warn)
stale_branchesmerged branches idle > --stale-days (warn)

--fail-on a,b requires specific checks — the rest become advisory.

Pairs with

git-master (act on the stale branches this finds), skill-audit (the same structural-hygiene idea, for agent skills), diff-review (the per-change gate; this is the per-repo gate).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free