Take5 Skill banner
metaWuming metaWuming

Take5 Skill

Development community

Description

A Claude Code skill that lets you say "Take 5" anytime and have Claude completely snapshot your development state — so when you come back days or weeks later and say "continue development", Claude picks up exactly where you left off.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

/take5 — Pause Your Work, Save State Completely

A Claude Code skill that lets you say "Take 5" anytime and have Claude snapshot your development state — so when you come back days or weeks later and say "continue development", Claude picks up exactly where you left off.

中文說明見下方 [中文版](#中文版)。


v2 — now diff-based

**If you used v1, the behaviour changed.** v1 ran the same seven steps every time. That's wrong once you have a real shipping workflow: by the time you invoke `/take5`, you've usually already committed, pushed, opened a PR and merged it. The old flow would run a full commit pass anyway, find nothing left but the diff on your memory files — and open a **second PR just for bookkeeping**.

Measured on a real project: **7 of the last 9 `/take5` PRs were pure bookkeeping** — they touched only `progress.md`, `TODOS.md` and `HANDOFF.md`. Meanwhile the feature PRs had already been updating those same files.

v2 replaces the linear ritual with a **delta check**. The guiding question is no longer "did I run all the steps?" but **"can the next session pick this up?"** If everything is already archived, the correct outcome is to do almost nothing.

What It Does

When you invoke `/take5`, Claude:

  1. **Flushes the session-title queue** — renames sessions queued by previous runs (see [Session auto-naming](#session-auto-naming))

  2. **Runs a delta check** — `git status`, `git log origin/..HEAD`, open PRs, and reads the top of your memory file to see whether this session's work is already recorded. Lands on one of four outcomes:

    Outcome Condition Action
    A — already archived clean tree, nothing ahead of remote, no open PRs, memory already current skip straight to the wrap-up
    B — bookkeeping only only memory/handoff files are dirty commit directly to the dev branch, no PR
    C — real code uncommitted code, config or migrations follow the project's normal PR flow
    **D — noise o