project-status
Skill8 starsChanged 4 months agoMITView on GitHub
Produce a 30-second situational-awareness briefing for any child project: tech stack, folder structure, git history, recent changes, deployment status, current state, link to wiki project page. Trigger: 'project status', 'status briefing', '/project-status'.
15 other projects use a version of this.
Adopted by
Most recently taken up by
- fabioc-aloha/Alex_ACT_ONEtheir own version, first seen Nov 15, 2026
- fullstackhouse/skillstheir own version, first seen Nov 15, 2026
- odytrice/metaskillstheir own version, first seen Nov 15, 2026
- eranw2000/claude-maintenance-skillstheir own version, first seen Nov 8, 2026
- desertcache/agent-ostheir own version, first seen Nov 1, 2026
- lautioliver/barrilete-kittheir own version, first seen Nov 1, 2026
Other versions15 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 15
- eranw2000/claude-maintenance-skills★ 8same name
- lautioliver/barrilete-kit★ 6same name
- AJBcoding/claude-skill-eval★ 4same name
- korchasa/flowai★ 3same name
- Manshooo/astral-genesis★ 3same name
- fullstackhouse/skills★ 1same name
- odytrice/metaskills★ 1same name
- philpalmieri/engineering-manager-skills★ 1same name
- Tracebrain/mcp★ 1same name
- desertcache/agent-os★ 0same name
5 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- demo-project/CLAUDE.mdCLAUDE.md
- project-template/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- close-weekSkill
- end-sessionSkill
- ingestSkill
- lintSkill
- new-engagementSkill
- plan-weekSkill
- querySkill
- review-sessionsSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 6 are distinctive, and 14 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
14
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
When the user says "project status", "status briefing", or invokes /project-status from inside any project directory (NOT memory itself), …
- Very specific: line 20
If the current project contains schema.md or memory/schema.md, it is the memory system or its installer.
- Distinctive: line 22
If no memory root resolves, continue the codebase briefing but mark the wiki page as unavailable instead of guessing a personal path.
- Very specific: line 34
Read AGENT.md for project overview and objectives
- Very specific: line 35
Read the project's page at {WIKI_ROOT}/wiki/projects/{project-slug}.md for lessons and reference, if it exists
- Very specific: line 37
Run: git log --oneline --since="2 weeks ago" for recent activity
- Very specific: line 38
Run: git log --oneline --all | tail -5 for the earliest commits
- Very specific: line 42
Run: git log -5 --format="%h %s (%ar)" for the last 5 commits with relative dates
- Very specific: line 43
Run: git diff --stat HEAD~3 to show what files changed recently (if enough commits exist)
- Distinctive: line 44
Check git status for any uncommitted work in progress
- Distinctive: line 45
Check for any open branches: git branch -a
- Distinctive: line 49
Check for deployment indicators and report what you find:
- Very specific: line 51
Azure (azd): check for azure.yaml, .azure/ folder, infra/ folder with Bicep files
- Very specific: line 52
GitHub Actions: check .github/workflows/ for CI/CD pipelines
- Very specific: line 53
Docker: check for Dockerfile, docker-compose.yml
- Very specific: line 54
Other CI/CD: check for .gitlab-ci.yml, Jenkinsfile, .circleci/, bitbucket-pipelines.yml
- Very specific: line 55
Git tags: run git tag --sort=-creatordate | head -5 for release/deploy tags
- Very specific: line 56
Last deploy: if azd is used, check .azure/ for environment state.
- Distinctive: line 57
If NO deployment config is found, say "No deployment configuration detected"
- Distinctive: line 101
Keep the entire briefing concise and scannable.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Project Status
When the user says "project status", "status briefing", or invokes /project-status from inside any project directory (NOT memory itself), produce a complete situational-awareness briefing so the user can get up to speed on that project in 30 seconds.
This skill is for any child project. When invoked from the memory system itself, refuse and direct the user to the wiki because the wiki is its status.
Coexists with the per-project
/statuscommand that ships in every scaffolded project under.claude/commands/status.md. The per-project version is Claude-Code-specific. THIS memory skill is the agent-agnostic version (works under GitHub Copilot CLI, Claude Code, or any tool that loads.github/instructions/). When both are available, prefer the per-project one if you are inside Claude Code (richer integration), otherwise use this skill.
Instructions
Gather information from ALL the sources below, then produce a single structured briefing. Use parallel tool calls to speed up the research.
Resolve the memory root
- If the current project contains
schema.mdormemory/schema.md, it is the memory system or its installer; refuse as described above. - Otherwise follow the memory-wiki path declared in the child project's
AGENT.md. - If no memory root resolves, continue the codebase briefing but mark the wiki page as unavailable instead of guessing a personal path.
1. Codebase analysis
- Tech stack: languages, frameworks, key dependencies (check
package.json,requirements.txt,pyproject.toml,*.csproj,Cargo.toml,go.mod,pom.xml, etc.) - Folder structure: high-level tree (max 2 levels deep), explain what each top-level folder contains
- Key files: entry points, config files, main modules
- Architecture patterns: monolith/microservices, API style (REST/GraphQL/gRPC), state management, key abstractions
- Size: approximate number of source files and lines of code
2. Project history — what we've done
- Read
AGENT.mdfor project overview and objectives - Read the project's page at
{WIKI_ROOT}/wiki/projects/{project-slug}.mdfor lessons and reference, if it exists - Summarise git log: total commits, contributors, major milestones
- Run:
git log --oneline --since="2 weeks ago"for recent activity - Run:
git log --oneline --all | tail -5for the earliest commits
3. Last modifications
- Run:
git log -5 --format="%h %s (%ar)"for the last 5 commits with relative dates - Run:
git diff --stat HEAD~3to show what files changed recently (if enough commits exist) - Check
git statusfor any uncommitted work in progress - Check for any open branches:
git branch -a
4. Deployment status
Check for deployment indicators and report what you find:
- Azure (azd): check for
azure.yaml,.azure/folder,infra/folder with Bicep files - GitHub Actions: check
.github/workflows/for CI/CD pipelines - Docker: check for
Dockerfile,docker-compose.yml - Other CI/CD: check for
.gitlab-ci.yml,Jenkinsfile,.circleci/,bitbucket-pipelines.yml - Git tags: run
git tag --sort=-creatordate | head -5for release/deploy tags - Last deploy: if azd is used, check
.azure/for environment state. If GitHub Actions, note the workflow files and what they do. - If NO deployment config is found, say "No deployment configuration detected"
5. Current state
- Current branch and how it relates to main/master
- Any uncommitted changes or stashed work (
git stash list) - Open TODO items in code: search for
TODO,FIXME,HACKin source files (report count, not each one)
Output format
Produce a briefing in this exact format:
## 🔍 Project Status: {project name}
### Tech Stack
{languages, frameworks, key deps — one line each}
### Architecture
{folder structure overview + patterns — keep it brief}
### History
- **Created:** {first commit date}
- **Total commits:** {count}
- **Recent activity:** {last 2 weeks summary}
### Last 5 Changes
{table: hash | message | when}
### Deployment
{deployment status, last deploy if known, CI/CD setup}
### Current State
- **Branch:** {current branch}
- **Uncommitted work:** {yes/no + summary}
- **Open TODOs:** {count}
### Wiki page
- Link to `{WIKI_ROOT}/wiki/projects/{slug}.md` (or note that it does not exist yet)
### Key Takeaways
{2-3 bullet points: what's the most important thing to know right now}Keep the entire briefing concise and scannable. No fluff. The user wants to read this in 30 seconds and know exactly where things stand.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

