// Use when the user wants to step through a feature's checkpoints chronologically, pausing at each step to ask questions. Triggers on phrases like "replay <feature>", "walk me through how X was built", "show me the journey of", "step me through how Y was implemented", and "replay the last week"
| name | replay |
| description | Use when the user wants to step through a feature's checkpoints chronologically, pausing at each step to ask questions. Triggers on phrases like "replay <feature>", "walk me through how X was built", "show me the journey of", "step me through how Y was implemented", and "replay the last week" |
Use entire search and entire explain to sequence checkpoints chronologically and walk through them step by step, pausing for questions at each step. The pause-and-ask interaction is the core feature — do not dump all steps at once.
Begin the first response to this skill invocation with the line:
Entire Replay:
followed by a blank line, then the content.
If the user wants a flat single-topic summary, use teach instead.
entire search, entire explain, and entire dispatch.entire search, entire explain, or entire dispatch as a single shell-quoted argument. Strip or escape embedded quotes, backticks, $(...), and ; before substituting into the command — never paste user text directly into a shell snippet.git rev-parse --is-inside-work-tree
entire version
Run this from inside a git repository.The Entire CLI is required but not installed. Install it from https://entire.io/docs/cli and try again.entire search, entire explain, and entire dispatch as authentication-gated. If any reports authentication is required, stop and tell the user:entire search requires authentication. Run entire login and try again.
Do not print Entire Replay: until at least the target-resolution search has succeeded.
entire search "<topic>" --json --limit 30 --date month
Sort the hits chronologically (ascending) by checkpoint timestamp.
First derive 1-2 seed terms by reading recent activity:
entire dispatch --since 7d --voice neutral
Pick the most recurring nouns from the dispatch as seed terms, then run focused searches in parallel:
entire search "<seed term>" --json --date week --limit 30
Sort hits chronologically (ascending).
entire explain --checkpoint <step-1-id> --full --no-pager
Fall back to --raw-transcript if --full fails.
Entire Replay:
Replaying: <topic or window>
Total steps: <n>
Date range: <first-date> -> <last-date>
Primary author(s): <name(s)>
---
## Step 1 of <n> · <date> · <author>
<one-line summary of this step>
**Why this step happened:** <1-2 sentences — what triggered it, what came before>
**Key change or decision:** <1-3 sentences — what was actually done>
Ready for step 2? (Or ask a question about this step.)
next, continue, yes, or any clear advance signal, fetch the next checkpoint's transcript and present the next step using the same shape, with one addition:Suppress the response header on these follow-up turns — only the first turn of the invocation includes it.
Questions about the current step: if the user asks a question instead of advancing, answer it from the current step's transcript only. Do not read ahead. End the answer with: Ready for step 2? (Or another question.) (use the correct step number).
After the final step: present a short closing block:
## Journey takeaways
- <takeaway>
- <takeaway>
- <takeaway>
3-5 takeaways, each one a generalization across the journey, not a restatement of a single step.
--date filter entirely and re-running. If still empty, say clearly: No checkpoints match "<target>". Tried: <queries and filters>. Do not invent steps.Only <n> checkpoints found — not enough for a replay. and suggest the teach or recall skills as alternatives.--full or --raw-transcript, drop the step and tell the user at that point in the sequence: Step <n> transcript unavailable — skipping to step <n+1>. Do not fabricate the missing step.Use when the user describes a task and wants to know whether something similar has been done before, then turn the closest prior session into a task playbook. Triggers on phrases like "have we done this before", "recall how we did X", "find similar work", "any precedent for", "has anyone solved", "is there a template for", and "how did we do this last time"
Use when a developer wants a topic-focused guided lesson built from canonical checkpoints, not a whole-repo overview. Triggers on phrases like "teach me <topic>", "teach me how this repo handles", "how does <topic> work in this repo", "give me a lesson on", "school me on", and "I need to learn about"
Use when an agent session ran outside the repo whose commits should record it — e.g. launched from a higher-level folder, a non-Entire repo, or one repo but editing another — to attach the session to each affected Entire-enabled repo's HEAD commit.
Use when the user wants to continue work from one agent in another agent, inspect recent sessions, or summarize a saved session or checkpoint for handoff
Explain why code looks the way it does by tracing the latest change for a file range or pasted snippet through `git blame` and deduplicated `entire explain` lookups. Use when the user asks what happened, says "tell me why" about a code block, is confused about a section of code, asks "wtf is going on", "why is this like this", "why was this changed", or wants provenance for a specific file block.
Explains the intent behind source code by finding original session transcripts. Use explain with a function, file, or line of code to understand why it exists.