Install
$ agentstack add skill-urmzd-dotfiles-repo-status ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: urmzd
- Source: urmzd/dotfiles
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.