issue-summary
Skill2 starsChanged 25 days agoApache-2.0View on GitHub
Show a dashboard of recent GitHub issue state for this repo — in-progress, in-review, open-and-untouched, and recently closed, with PR links and CI/review status where applicable. Use whenever the user says "/issue-summary", "what's the state of the backlog", "what's in progress", "what issues are open", or wants a quick view of recent issue/PR activity without scrolling raw `gh issue list`/`gh pr list` output.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- EdoMon93/claude-skillstheir own version, first seen Oct 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- EdoMon93/claude-skills★ 0same 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
- announce-releaseSkill
- sdlcifySkill
- work-issueSkill
The file
Files
issue-summary — dashboard of recent issue state
This is a thin wrapper: it runs scripts/issue_summary.sh and shows
its output verbatim. The script does all the actual gh/jq work
(fetching issues and PRs, matching PRs to issues via their Closes
#N/Fixes #N/Resolves #N body text, grouping by status) — there is
no reasoning to do here, and no reason to re-derive any of it by
hand. If the script's output looks wrong, fix the script; don't
paper over it by reasoning about the data in this skill instead.
Run it
./scripts/issue_summary.shPass --closed N to change how many recently-closed issues are shown
(default 10):
./scripts/issue_summary.sh --closed 20Print the script's stdout to the user as-is (it's already formatted
markdown, grouped into In Progress / In Review / Open / Recently
Closed). Requires gh authenticated against this repo's remote.
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.