| name | vs-recap |
| description | Create a tiny out-of-context recap of the current situation and recent changes. Use when the user says /vs-recap, recap, catch me up, where are we, out of context, I have no context, or explain what is going on. |
Recap
Give the user a compact handoff for a reader who just arrived from another topic.
Use When
- The user says
/vs-recap, vs-recap, catch me up, where are we, out of context, I have no context, explain what is going on, or asks for recent
changes.
- The user needs enough context to decide the next step, not a full history —
whether they followed the session so far or are arriving cold.
Gather
Use the best current evidence available, in this order:
- Current conversation state and tool results.
- Git diff, recent commits, or changed files if the recap is about repo work.
- Relevant local artifacts mentioned in the conversation.
Do not do broad archaeology unless the user asks. Prefer live repo evidence over memory.
Write
Output at most a few sentences. Optimize for decision-making:
- What changed or was learned.
- Why it matters now.
- Any blocker, risk, or open decision that affects the next step.
Avoid implementation trivia, long file lists, praise, and process narration. If nothing material changed, say that plainly.
End With Actions
End with Possible actions: followed by 2-4 concise options. Each option should be an action the user can choose immediately.
Example:
We added the `vs-recap` skill as a standalone marketplace skill and wired the VS plugin to reuse it, so `/vs-recap` can travel with VS without duplicating instructions. Validation passes, and the only remaining decision is whether to ship this as-is or add behavior eval coverage.
Possible actions: create PR, add eval, adjust wording, stop here.
Workflow
Direct: emit Next only. Composed: return to caller.
Prev: context switch | interrupted task
Next: done
Relevant: /vs-ship-it | /vs-brief
