resume

Summarizes git branch state, recent commits, and scratch notes for worktree orientation.

Updated Jul 28, 2026
One-click install
npx skills add https://github.com/vinzenz/workflows --skill resume-vinzenz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resume
Source: https://github.com/vinzenz/workflows/tree/main/.agents/skills/resume
Command: npx skills add https://github.com/vinzenz/workflows --skill resume-vinzenz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agent or developer reopens a repository after a break, reconstructing context normally requires running several separate git commands (status, log, diff, branch) and remembering what was in progress. This Skill collapses that into one read-only orientation call and provides a durable on-disk scratch note that survives crashes and context-window resets. ## Core Features & Use Cases - One-call orientation snapshot: Shows branch, upstream divergence, working-tree summary, and commits since the last acknowledged point, capped and summarized. - Durable scratch note: Append timestamped one-line notes per worktree with resume note, read them back next session, and clear them when done. - Explicit cursor control: resume ack records what has been seen; the home view never advances the cursor silently, and detached HEAD or shallow clones are handled gracefully. - Use Case: An agent starting a new session in a previously used worktree runs resume to see the branch, uncommitted changes, five new upstream commits, and its own note saying "mid-refactor of parser module", then continues work without re-investigating. ## Quick Start Ask the agent to run resume in the current repository to get an orientation snapshot of branch state, recent commits, and any saved scratch note.

Frequently Asked Questions about resume

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

FAQPage Schema
How do I quickly see what changed in a git repo since my last session?▼

Run resume in the repository to get a single snapshot covering branch, upstream divergence, working-tree summary, and commits since your last acknowledged point. The commit list is capped and summarized rather than showing full history.

How do I keep a persistent note for a git worktree between sessions?▼

Use resume note followed by your text to append a timestamped line to a per-worktree scratch note stored on disk. The note survives crashes and context resets, and resume note --clear resets it.

Does resume work with multiple git worktrees or parallel agents?▼

Yes, state is stored per worktree using git rev-parse --git-path, so multiple agents working in separate worktrees never collide. Each worktree maintains its own cursor and scratch note independently.

What happens with resume on a detached HEAD or shallow clone?▼

Detached HEAD gets an ephemeral commit-scoped cursor that does not follow you to other checkouts, and resume says so explicitly. A shallow clone whose history no longer reaches the last cursor is reported as such and falls back to recent HEAD history.

When should I not use resume for session context?▼

Avoid resume for multi-session planning or ticket breakdowns, which belong to planning skills, and for searching past session transcripts or commands run, which belongs to agent-log. Its note is a one-line-per-entry scratchpad, not a plan or transcript index.