specstory-session-summary
Summarize recent SpecStory AI coding sessions in standup format. Use when the user wants to review sessions from .specstory/history, prepare for standups, track work progress, or understand what was accomplished.
npx skills add majiayu000/claude-skill-registry --skill specstory-session-summary --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.
## Context You will analyze recent SpecStory session history files to provide a standup-style summary. Argument provided: `$ARGUMENTS` (default: 5 sessions, or "today" for today's sessions only) ## Your Task ### Step 1: Find Recent Sessions First, check if the SpecStory history folder exists and list recent session files: ```zsh ls -t .specstory/history/*.md 2>/dev/null | head -20 ``` **If no `.specstory/history` folder exists or it's empty**, respond with: > No SpecStory session history found in this directory. > > SpecStory automatically saves your AI coding sessions for later reference. To start recording your sessions, install SpecStory from https://specstory.com Then stop - do not proceed with the remaining steps. **If sessions are found**, continue with the analysis. If the argument is "today", filter to today's date. Otherwise use the number provided (default 5). ### Step 2: Read and Analyze Each Session Session files can be very large and may contain multiple user requests. Use this chunked reading strategy: **Step 2a: Understand the session structure** First, grep for all user message markers to see the session's scope: ``` grep -n "_\*\*User\*\*_" <file> | head -10 ``` Th
- Context
- Your Task
- Step 1: Find Recent Sessions
- Step 2: Read and Analyze Each Session
- Step 3: Format Output
- Step 4: Summary Section
- Guidelines
- Example Output
ls -t .specstory/history/*.md 2>/dev/null | head -20
What does the specstory-session-summary skill do?
Summarize recent SpecStory AI coding sessions in standup format. Use when the user wants to review sessions from .specstory/history, prepare for standups, track work progress, or understand what was accomplished.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill specstory-session-summary --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.