Feature request: built-in /recap command for session context

Resolved 💬 5 comments Opened Mar 15, 2026 by leap21ai Closed Apr 12, 2026

When working across 10+ terminal windows on different projects, it's easy to lose track of what was done where. A built-in /recap command that summarizes the current session would help.

I built this as a custom skill in about 2 minutes, but a native version would have direct access to the conversation history and be more reliable.

What it would show:

  • Project name and branch
  • Bullet list of what was done
  • Commits made
  • Deployments
  • Open items

Skill definition I'm using today:

---
name: recap
description: Quick recap of what was done in this session and which project
user_invocable: true
---

# /recap — Session Recap

Give a concise recap of the current session. Include:

1. **Project**: the repo name and branch (from git)
2. **What was done**: bullet list of completed actions, max 1 line each, plain language
3. **Commits**: list any commits made this session (short hash + message)
4. **Deployed**: list any deployments (service name + URL)
5. **Open items**: anything unfinished or flagged for follow-up

Rules:
- Keep the entire recap under 20 lines
- Use plain language a non-engineer could scan
- No code blocks, no file paths, no technical jargon unless unavoidable

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗