
Status
- 604 installs
- 1 repo stars
- Updated May 26, 2026
- camacho/ai-skills
status is an agent skill that generates a read-only project status dashboard with git activity, open issues, active plans, branches, worktrees, and memory usage for developers catching up on repo state.
About
status is a camacho/ai-skills agent skill that builds a concise project status report without modifying the repository. It collects git state in parallel—recent oneline commits, sorted branches, and worktree info—alongside open issues, active plans, memory state, and scratchpad contents. Developers invoke status when they ask "what's going on", "where are we", or want a faster alternative to full /catchup reconstruction. The skill is intentionally read-only: it snapshots current project health so engineers can orient before picking the next task.
- Combines git log, branches, worktrees, and status into one view
- Pulls the 20 most recent open GitHub issues plus recently closed ones
- Scans ai-workspace/plans for active non-.done.md plan files and their Status fields
- Reports MEMORY.md line count against the 200-line limit
- Read-only dashboard that runs in parallel where possible
Status by the numbers
- 604 all-time installs (skills.sh)
- Ranked #666 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/camacho/ai-skills --skill statusAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 604 |
|---|---|
| repo stars | ★ 1 |
| Security audit | 2 / 3 scanners passed |
| Last updated | May 26, 2026 |
| Repository | camacho/ai-skills ↗ |
How do you get a quick project status snapshot?
Get an instant, consolidated snapshot of project state including git activity, open issues, active plans, and memory usage.
Who is it for?
Developers returning to an active repo who need a fast, read-only overview without running full catchup reconstruction.
Skip if: Teams needing deep code archaeology, automated CI health checks, or write operations on issues and branches.
When should I use this skill?
The user asks for a status report, project overview, what's going on, or where the project stands.
What you get
Consolidated status report covering git log, branches, worktrees, issues, plans, and memory state.
- Project status dashboard
- Git and issue summary
By the numbers
- Reads the 10 most recent git commits and up to 15 branches per status run
- Gathers git state, issues, plans, memory, and scratchpad in parallel
Files
Project Status Report
Generate a concise project status dashboard. This is a read-only snapshot — it doesn't modify anything.
Data Collection
Gather these in parallel where possible:
1. Git State
REPO_ROOT="$(git rev-parse --show-toplevel)"
git -C "$REPO_ROOT" log --oneline -10
git -C "$REPO_ROOT" branch -a --sort=-committerdate | head -15
git -C "$REPO_ROOT" worktree list
git -C "$REPO_ROOT" status --short2. GitHub Issues
# Open issues, sorted by most recent
gh issue list --state open --json number,title,labels,updatedAt --limit 20
# Recently closed (last 7 days)
gh issue list --state closed --json number,title,closedAt --limit 10 | jq '[.[] | select(.closedAt > (now - 604800 | todate))]'If gh is not authenticated, skip this section and note "GitHub CLI not authenticated — issue data unavailable."
3. Active Plans
Check "$(git rev-parse --show-toplevel)/ai-workspace/plans/" for any non-.done.md plan files. Read their Status field.
4. Memory State
- Read
"$(git rev-parse --show-toplevel)/ai-workspace/MEMORY.md"— note line count vs 200-line limit - Check
"$(git rev-parse --show-toplevel)/ai-workspace/.last-reflect-ts"— how long since last /reflect - Check
"$(git rev-parse --show-toplevel)/.branch-context.md"— any uncommitted learnings
5. Scratchpad
Read "$(git rev-parse --show-toplevel)/ai-workspace/scratchpad.md" — count - [ ] items awaiting elevation.
Output Format
Present as a compact dashboard. Adapt the sections based on what data is available — skip sections with no content rather than showing empty tables.
## Project Status: <repo-name>
### <date>
**Branch**: <current branch> | **Mode**: <autonomous/copilot> | **Last reflect**: <relative time>
### Open Issues (<count>)
| # | Title | Labels | Updated |
|---|-------|--------|---------|
(most recent 10, sorted by updated)
### Recently Closed (<count>, last 7d)
- #N title (closed <date>)
### Active Work
- Branches: <list active non-main branches>
- Worktrees: <list linked worktrees>
- Plans in progress: <list non-.done.md plans>
### Health
- MEMORY.md: <line count>/200 lines
- Scratchpad: <N> items flagged for elevation
- Last reflect: <timestamp or "never">
- .branch-context.md: <exists with N lines / not found>
### Suggested Next
(Pick 2-3 based on what you see — e.g., stale issues, scratchpad items to elevate, overdue reflect, MEMORY.md near limit)The "Suggested Next" section is the most valuable part — it turns a passive report into actionable guidance. Base suggestions on:
- Issues with no recent activity
- [ ]scratchpad items that should become issues- MEMORY.md approaching 200 lines (needs pruning)
- Long time since last /reflect
- Branches with no recent commits (stale work)
- Open issues that match recently completed work (may be closeable)
Related skills
How it compares
Pick status for a lightweight snapshot instead of full session catchup or deep git bisect workflows.
FAQ
Does status modify the repository?
status is read-only and only queries git logs, branches, worktrees, issues, and memory state to produce a snapshot without changing project files or configuration.
What git data does status include?
status gathers the 10 most recent oneline commits, up to 15 branches sorted by committer date, and active worktree information from the repository root.
Is Status safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.