session-recap
Recap changes, files, decisions, and pending user calls since the last message or across past sessions. Use when returning to work; use droid search, droid resume, or session-navigation to find, list, or resume sessions.
Cynnamoroll · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add Cynnamoroll/factory-stack --skill session-recapAbout this skill
name: session-recap description: "Recap changes, files, decisions, and pending user calls since the last message or across past sessions. Use when returning to work; use droid search, droid resume, or session-navigation to find, list, or resume sessions." license: MIT compatibility: droid allowed-tools:
- Read
- Grep
- Glob
- Execute
Session recap
Recap every pending user call so the reply alone supports a decision. Assume they remember only their last message. Stay read-only, with no jobs or external posts.
1. Gather
- This session. Your work since the user's last message, subagent reports, and the current state of each branch, PR, CI run, or worktree the session touched (
git status,git log,gh pr view). - Past sessions.
droid search "<topic>" --jsonfinds them. Read the matching turns. If the user wants to continue one, point them atdroid resume.
Check each number you will show against its source.
Action items are user-only calls (product choices, approvals, irreversible steps, missing access), not work you can do. Never invent one.
2. Write
- Open with one sentence that names what waits on the user, or says nothing does.
- What happened, in under 100 words. One plain bullet per thing the user asked for: what came of it and whether it is done, running, failed, or unchecked. "Search was slow from a missing index", not "Search review: done."
- Add a
mermaiddiagram only when a picture explains a change better than sentences (a PR stack, a flow before and after). At most six boxes. - Then the action items. For each, the call, your pick, what it changes for users, the evidence, and the risk. Give the PR or issue number. For a choice between options, give each option's gain and cost.
Use plain words. Leave out hashes, paths, and commands unless the user needs one to act.
Done when
Every action item still waiting on the user is listed with a pick, every status line stays true read alone, nothing marked done still waits on the user, and no file changed.