agentleFS
Sign inStart free
hosaypenghosaypeng/claude-skills/git-status/SKILL.md

git-status

Skill0 starsChanged 8 days agoMITView on GitHub

Scan all local git repositories for uncommitted changes, unpushed commits, and stale branches. Use when user says 'check my repos', 'git status all', 'any unpushed changes', 'repo health check', 'stale branches', or 'what needs committing'.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. cognis-digital/skillsmith★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository7 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check the commit, push, and branch health of all git repos under $HOME.

    line 10
  2. Distinctive:

    Run the repo discovery script to find all git repos, excluding noise directories:

    line 14
  3. Distinctive:

    If a specific repo path was provided as an argument, pass it through for the single-repo fast path:

    line 20
  4. Very specific:

    If find_repos.sh fails, fall back to find ~ -name .git -type d -maxdepth 5 excluding node_modules and .cache.

    line 26
  5. Very specific:

    Use ~ shorthand for $HOME in paths for readability.

    line 49
  6. Distinctive:

    Stale branch script returns nothing: All branches have recent commits — this is normal.

    line 56

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Git Status Checker

Check the commit, push, and branch health of all git repos under $HOME.

Instructions

  1. Run the repo discovery script to find all git repos, excluding noise directories:
bash ~/.claude/skills/git-status/scripts/find_repos.sh

If a specific repo path was provided as an argument, pass it through for the single-repo fast path:

bash ~/.claude/skills/git-status/scripts/find_repos.sh /path/to/repo

If find_repos.sh fails, fall back to find ~ -name .git -type d -maxdepth 5 excluding node_modules and .cache.

  1. For each repo found, check three things:
  • Uncommitted changes: git -C <repo> status -s 2>/dev/null
  • Unpushed commits: git -C <repo> log @{u}.. --oneline 2>/dev/null
  • Stale branches: bash ~/.claude/skills/git-status/scripts/stale_branches.sh <repo> 7
  1. Report a summary grouped into:
  • Clean repos — nothing uncommitted, nothing unpushed, no stale branches (just list names)
  • Repos with uncommitted changes — show file count and repo path
  • Repos with unpushed commits — show commit count and repo path
  • Repos with stale branches — show branch name, last commit date, and age in days. Format as a table:
| Repo   | Branch          | Last commit | Age  |
| ------ | --------------- | ----------- | ---- |
| ~/Code/foo | feature/old  | 2026-02-15  | 22d  |

Skip main and master from the stale branch report — they may be inactive but are not candidates for cleanup.

Use ~ shorthand for $HOME in paths for readability. Keep output concise.

Troubleshooting

  • Repo discovery takes very long: The script may be traversing large directories. Verify it excludes node_modules, .cache, and Library.
  • "fatal: not a git repository" for some paths: Skip corrupted repos and note them in output.
  • No upstream configured: Skip the unpushed check for those repos and note "no upstream configured."
  • Stale branch script returns nothing: All branches have recent commits — this is normal. Only report the stale branches section if there are results.

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