status
Display concise project status including git state, latest commits, open issues, and active plans. TRIGGER when: user asks for project status, current state, what's happening, progress check, or "where are we". DO NOT TRIGGER when: user wants detailed overview (use /overview), or wants to start/finish issues.
Profile →npx skills add majiayu000/claude-skill-registry --skill status-aifuun-u-safe --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Status - Quick Project Status Check Display structured project status in ~300 words across three time horizons: - **Long-term/Global** (~100 words): Project purpose and goals - **Mid-term** (~100 words): Recent 5 issues/features progress - **Short-term/Current** (~100 words): Current/adjacent issue status and blockers ## Purpose Provide layered context from strategic vision to tactical execution: - **Global view**: What is this project fundamentally about? - **Recent history**: What have we been working on? (last 5 issues) - **Current focus**: What's happening right now? What's blocked? **When to use**: Session start, context switch, or progress check. **When NOT to use**: For detailed metrics and comprehensive reports, use `/overview` instead. ## Workflow ### 1. Gather Long-term Context Read project overview from `CLAUDE.md` or `README.md`: ```bash # Get project description (first paragraph or ## What Is This section) head -50 CLAUDE.md | grep -A 10 "## 🎯 What Is This Project" ``` Extract: Purpose, tech stack, architecture pattern (≤100 words). ### 2. Gather Mid-term Context (Recent 5 Issues) ```bash # Recently closed issues (last 3) gh issue list --state closed --limit 3 --jso
- Purpose
- Workflow
- 1. Gather Long-term Context
- 2. Gather Mid-term Context (Recent 5 Issues)
- 3. Gather Short-term Context (Current Issue)
- 4. Format Three-Layer Output (~300 words)
- 5. Present to User
- Output Format Rules
- Integration
- Examples
- Example 1: AI Development Framework (ai-dev project)
- Example 2: Active Development (with uncommitted changes)
- Performance
- Best Practices
Get project description (first paragraph or ## What Is This section) head -50 CLAUDE.md | grep -A 10 "## 🎯 What Is This Project" Recently closed issues (last 3) gh issue list --state closed --limit 3 --json number,title,closedAt Currently open issues (next 2-3) gh issue list --state open --limit 3 --json number,title,labels Current branch (might indicate active issue) git branch --show-current Working directory status git status --short
What does the status skill do?
Display concise project status including git state, latest commits, open issues, and active plans. TRIGGER when: user asks for project status, current state, what's happening, progress check, or "where are we". DO NOT TRIGGER when: user wants detailed overview (use /overview), or wants to start/finish issues.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill status-aifuun-u-safe --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.