status
Project status dashboard — open issues, recent commits, active branches/worktrees, memory state, and scratchpad. Use when the user asks for a status report, project overview, "what's going on", "where are we", or wants to catch up on project state without the full /catchup reconstruction.
- Installs
- 604
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/camacho/ai-skills --skill status- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads status automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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 --short
2. 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)
FAQ
What does the status skill do?
Project status dashboard — open issues, recent commits, active branches/worktrees, memory state, and scratchpad. Use when the user asks for a status report, project overview, "what's going on", "where are we", or wants to catch up on project state without the full /catchup reconstruction.
How do I install status?
Run npx skills add https://github.com/camacho/ai-skills --skill status in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/status/ (personal) or .claude/skills/status/ (project).
Which AI agents can use status?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is status safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains status?
It is published by camacho in camacho/ai-skills. It has 604 recorded installs.
More from camacho/ai-skills
archive
camacho/ai-skills
Fills Outcomes & Learnings in a plan file and renames it to .done.md.
bail
camacho/ai-skills
Reflects, updates GitHub Issue, closes PR if open, cleans up worktree/branch.
capture
camacho/ai-skills
Creates a draft GitHub Issue with triage label from natural language description.
plan-review
camacho/ai-skills
Auto-assembles review panel using deterministic rules, dispatches agents against plan file, collects verdicts.
orient
camacho/ai-skills
Fetches issue context, auto-detects task type, maps to branch prefix, presents brief.
reflect
camacho/ai-skills
Use after merging a branch or completing a task to consolidate learnings into memory layers, close out issues, and verify the phase gate.
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.