recap

Recap

Everything needed is already in context. This skill is fast because it refuses to go looking for anything else.

Speed contract

Run exactly one command, and only if the working directory is a git repository:

git status --short --branch && git --no-pager log --oneline -10

If it fails (not a repository), continue silently without it.

Never call Read, Grep, Glob, Edit, WebSearch, or any other tool. Never re-open files that were already discussed — the discussion is in context. Never launch a subagent. One command, then write the answer.

Language

Write the recap in the language the user has been writing in this session, not the language of this skill. Mixed input follows the dominant language of the user's own messages. Translate the slot labels too — in Russian they read Цель / Сделано / Сейчас / Открыто / Дальше. Keep identifiers verbatim — file paths, branch names, commands, flags, library names, error strings.

Level 1 — default output

No argument means the full status. Fill these five slots, in order:

Goal — what the user is actually trying to achieve, in their terms. One line. If the session pivoted, state the current goal and mark the pivot in a clause.

Done — 2–5 bullets, one line each. Each bullet is a result, not an activity: "found the built-in /recap, it is one line long" rather than "searched for skills". Where a decision was made, name the decision and its reason. Merge related steps into one bullet.

Now — the single thing in flight and how far it got. If the last turn completed cleanly, name that completed thing instead.

Open — 0–3 bullets of what is expensive to rediscover: approaches tried and rejected with the reason, unanswered questions, known traps, work deliberately deferred. Omit the whole slot when genuinely empty — never pad it.

Next — the immediate next action, concrete enough to start on. If a user decision is required first, name the decision instead.

Close with a one-line hint that any slot or topic can be expanded.