repo-activity-summary
Skill1 starsChanged 5 months agoMITView on GitHub
Use when the user asks to summarize repo activity, check project status, gauge progress, list open issues and PRs, or see CI health. Triggers on "activity summary", "what's open", "project status", "progress check", "CI status".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- CodeAlive-AI/ai-driven-developmenttheir own version, first seen Sep 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- CodeAlive-AI/ai-driven-development★ 169same name
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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- site/llms-full.txtllms.txt
- site/llms.txtllms.txt
- work-planSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Run all three gh commands in parallel:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Repo Activity Summary
Summarize current repository activity — open issues, pull requests, and CI status — in one structured report. Uses the gh CLI against the current repo.
Data Gathering
Run all three gh commands in parallel:
Open Issues (top 15)
gh issue list --state open --limit 15 \
--json number,title,labels,milestone,updatedAt \
--jq '.[] | "\(.number)\t\(.title)\t\(.labels | map(.name) | join(","))\t\(.milestone.title // "none")\t\(.updatedAt[:10])"'Open Pull Requests
gh pr list --state open --limit 10 \
--json number,title,headRefName,createdAt,isDraft,statusCheckRollup \
--jq '.[] | "\(.number)\t\(.title)\t\(.headRefName)\t\(.createdAt[:10])\t\(.isDraft)\t\(.statusCheckRollup | map(.conclusion // .status) | join(","))"'Recent CI Runs (last 8)
gh run list --limit 8 \
--json name,status,conclusion,headBranch,createdAt,event \
--jq '.[] | "\(.conclusion // .status)\t\(.name)\t\(.headBranch)\t\(.createdAt[:10])\t\(.event)"'Output Format
Present results as three markdown tables with a planning summary:
## Open Issues (N)
| # | Title | Milestone | Labels |
[sorted by number descending — newest first]
Breakdown: X on milestone-A, Y on milestone-B. Highlight P0/P1 items.
## Open Pull Requests (N)
| # | Title | Branch | Draft? | CI |
[note any failing checks]
## CI Status (Recent Runs)
| Status | Workflow | Branch |
[flag any failures prominently]
## Current Branch Context
[git branch name + uncommitted file count from git status]
## Planning Takeaways
[2-4 bullet points: blockers, active work, items needing attention]Common Mistakes
| Mistake | Fix |
Using checks field on gh pr list | Use statusCheckRollup instead — checks is not a valid JSON field |
| Not handling empty results | If no open PRs, say "No open pull requests" instead of an empty table |
| Forgetting current branch context | Always include git branch --show-current and uncommitted file count |
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.