urmzd/dotfiles / dot_agents/skills/repo-status
repo-status
VerifiedScan a folder of git repos and report each repo's local dirty/clean state, ahead/behind divergence from upstream, recent activity, and latest CI run status. Read-only: never commits, pushes, or edits. Defaults to the folder argument or your repo root. Use when checking "what's live", "which repos are dirty", or "repo status across my projects". Sibling skills overlap on folder scanning: do NOT use for "what should I work on next" prioritization (use get-work); do NOT use for a recent-activity-only overview without dirty/CI detail (use status). repo-status is the local dirty/ahead/behind + CI-state report.
Repo Status
Scan a directory for git repositories with recent activity and report their status.
Invocation
The user may pass a folder path as an argument. Default to $REPO_ROOT, falling back to ~/github if unset.
Steps
-
Discover repos: Find all directories containing a
.gitfolder (one level deep only; do not recurse into nested repos). -
Filter by activity: Only include repos that have commits in the last 7 days on any local branch (
git log --all --since='7 days ago' --oneline -1). Skip repos with no recent activity. -
For each active repo, gather:
- Repo name (directory basename)
- Current branch vs default branch (use
gh repo view --json defaultBranchRef -q .defaultBranchRef.nameor fall back to checking for main/master) - Uncommitted changes:
git status --porcelain(staged, unstaged, untracked counts) - Unpushed commits: commits ahead of upstream (
git rev-list @{u}..HEAD --count 2>/dev/null) - Behind upstream: commits behind (
git fetch --quiet && git rev-list HEAD..@{u} --count 2>/dev/null) - CI status:
gh run list --limit 1 --json status,conclusion,name. Show latest workflow run status (passing/failing/in-progress)
-
Output format: Print a clean, grouped summary. For each repo use this structure:
## repo-name [branch: feature/xyz -> main]
- Status: 3 modified, 1 untracked
- Ahead: 2 commits unpushed
- Behind: 5 commits (needs pull/rebase)
- CI: passing | failing (ci.yml) | in progress
- Action needed: pull, push, commit changes, fix CI
- Summary table at the end: one-line-per-repo showing repo name, branch, dirty/clean, ahead/behind counts, CI status, and action needed.
Rules
- Run
git fetch --quietbefore checking ahead/behind so counts are current. - Run repo checks in parallel where possible (use
&andwaitin bash). - If a directory isn't a valid git repo or has no remote, note it and move on.
- Keep output concise; skip sections that have nothing to report (e.g., don't show "Behind: 0").
- Only show repos with recent activity (last 7 days) to keep the report focused.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |