recap

Generate a structured end-of-session summary of completed work, findings, and next steps.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill recap-sassy-dog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: recap
Source: https://github.com/Sassy-Dog/sassydog-skills/tree/main/skills/recap
Command: npx skills add https://github.com/Sassy-Dog/sassydog-skills --skill recap-sassy-dog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a long working session, it is hard to remember exactly what shipped, what issues surfaced, and what still needs attention. This Skill produces a consistent, evidence-based session recap so you can scan the outcome instead of re-reading the entire conversation. ## Core Features & Use Cases - Fixed recap format: Renders four sections every time — work completed, what surfaced, issues worth filing, and immediate next steps — so reports are predictable and scannable. - Evidence-grounded reporting: Every completed item carries proof (PR number, commit SHA, run id), and uncertain states are re-verified with quick checks like gh pr view before being asserted. - Issue triage without mutation: Proposes GitHub issues for untracked signals with titles, labels, and rationale, but never files or edits anything itself. - Use Case: At the end of a day where you merged two PRs, hit a flaky test, and left one PR awaiting review, ask for a recap and get a dated report listing the merges with evidence, the flaky test as a surfaced finding, and "merge PR #13" as the top next step. ## Quick Start Ask the assistant to recap the session and summarize what we got done today.

Frequently Asked Questions about recap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize what was accomplished in a coding session?▼

Ask for a recap of the session. The skill walks the session once, sorts events into work completed, findings surfaced, issues to file, and next steps, then renders a fixed markdown report with evidence like PR numbers and commit SHAs.

How to generate an end-of-day work summary from an AI session?▼

Trigger the recap with phrases like "recap the day" or "wrap up the session". It produces a dated report with completed work, notable findings, proposed GitHub issues, and ordered next steps including literal commands for one-liners.

Does the recap skill file GitHub issues automatically?▼

No, the skill is strictly read-only and never files or edits issues. It only recommends issues worth filing with proposed titles and labels; actual filing is routed through the separate github-issues skill after user approval.

Can the recap report unverified claims about merged PRs?▼

No. Before asserting terminal states like "merged" or "closed", the skill re-checks them with quick reads such as `gh pr view` or `gh issue view` if the last observation is stale. Uncertain items render as uncertain rather than inferred.

What happens if nothing was completed during the session?▼

The work completed section always renders and honestly states that nothing shipped. Empty optional sections are dropped entirely, while an empty next-steps section usually indicates the gather step missed something.