Refresh README · Entire
Refresh README
c264cf9→main·
Sessions
Transcript data is unavailable for this checkpoint.
Changes
1
- MREADME.md+147/-123
Skills
Cross-agent skills and commands powered by Entire. Bring your Entire context to your agents with cross-agent skills.
Skills
Why This Exists
session-handoff
The Entire CLI captures the context behind your code changes: prompts, transcripts, Checkpoints, and the decisions that led to each change, alongside your git history. This repository packages agent-invokable workflows that teach coding agents how to use that context across development environments.
Reads Entire session metadata and helps move work from one agent to another without making the user reconstruct the context manually. Instead of looking up Entire commands yourself, you can ask in plain language and let your agent search prior work, inspect provenance, hand off session state, or turn repeated workflows into new skills.
Current behavior:
Install
- auto-detects the most recent session from
.git/entire-sessions/ - reads the raw transcript at the path stored in session metadata
- produces a structured compaction summary (Task Overview, Current State, Important Discoveries, Next Steps, Context to Preserve) instead of dumping raw transcript lines
- surfaces unanswered questions from the previous agent for the user to answer
- supports checkpoint handoff via
entire explain --checkpoint <id> --full --no-pager - falls back to
entire explain --checkpoint <id> --raw-transcript --no-pagerif full output is unavailable - resolves checkpoints from: local
entire/checkpoints/v1branch,.entire/settings.jsoncheckpoint_remote, or nearby local clone - filters sessions by agent name (e.g. "codex", "gemini") when mentioned Install every skill with the skills CLI:
session-to-skill
npx skills add https://github.com/entireio/skills --all
Turns Entire session history into a focused reusable skill draft without making the user manually find, paste, or reconstruct old agent conversations. Install one skill:
Current behavior:
npx skills add https://github.com/entireio/skills --skill search
- asks what reusable behavior the user wants to extract before reading transcripts
- accepts an explicit session ID or checkpoint ID when the user already has one
- searches Entire history with
entire search "<query>" --jsonwhen the user describes a repeated workflow - expands selected checkpoints with
entire explain --checkpoint <id> --full --no-pager - reads active session metadata from
.git/entire-sessions/<session-id>.jsonwhen needed - extracts durable lessons such as repo conventions, validation commands, user corrections, required inputs, and behaviors to avoid
- drafts a focused
SKILL.mdinstead of recapping the whole session - asks before writing, installing, or overwriting a skill
What These Skills Help Agents Do
| Goal | Example prompt |
|---|---|
| Find prior work before making changes | search past work for the migration |
| Understand the intent behind a function, file, or line | /explain parseConfig |
| Investigate the latest change to a specific block | what happened at src/auth.ts:42 |
| Pick up another agent's work | hand off the codex session |
| Convert repeated work into a reusable workflow | make a skill from this session |
Included Skills
The current repository includes these skills. Each skill lives in skills/<skill-name>/SKILL.md.
search
Finds prior work in your Entire history by topic, repo, branch, author, or time window, so your agent can bring past context into the current task before making changes.
explain
Traces source code back to the original conversation where it was created. Use /explain with a function, file, or line of code to understand why it exists.
Current behavior:
- identifies the commit that introduced the code via git blame/log
- reads the session transcript via
entire explain --no-pager --commit <sha> - works with functions, files, and individual line changes
- reports clearly when code is untracked, uncommitted, or created outside an Entire session
what-happened
Explains what happened to a specific code block by tracing the latest change for a file line, range, or pasted snippet through git blame and Entire checkpoints.
session-handoff
- resolves file lines, ranges, or pasted snippets to exact line numbers
- asks for a concrete file line, range, or snippet before running provenance commands
- deduplicates commit and checkpoint lookups before running expensive transcript commands
- asks before expanding broad ranges with many unique commits
- summarizes
entire explainoutput without dumping raw transcripts by default; raw transcript expansion is opt-in - falls back to clearly labeled current-code analysis when checkpoint-backed context is unavailable
Examples:
session-to-skill
- "tell me why this code is like that"
- "why does this code look like this?"
- "what happened here:
src/auth.ts:42-57" - "what happened at
src/auth.ts:42" - "what happened to this block?" plus a pasted snippet
search
Requirements
Searches Entire checkpoint history and transcripts to find prior work by topic, repo, branch, author, or time window. These skills are designed for repositories where Entire has captured useful history. Some workflows need:
Current behavior:
the Entire CLI installed
a git repository with Entire sessions, Checkpoints, or Checkpoint-backed commits
entire loginfor workflows that search indexed historya GitHub
originand pushed, indexed Checkpoints for remote search resultsruns
entire search "<query>" --jsonand summarizes the top matchessupports filters:
--repo,--branch,--author,--date, and inline query filters likeauthor:<name>,date:weekdrills into a specific result with
entire explain --checkpoint <id> --full --no-pagerbroadens searches progressively when initial results are empty (remove branch filter, widen date, simplify terms)
Installation
Install with skills CLI (universal, works with any Agent Skills-compatible tool):
npx skills add https://github.com/entireio/skills --all
# or a single skill:
npx skills add https://github.com/entireio/skills --skill session-handoff
Contributing
Natural language examples: See CONTRIBUTING.md for local development, validation, and pull request guidance. Please also follow the Code of Conduct.
Support
Checkpoint Resolution
For bugs, feature requests, or questions, open a GitHub issue. You can also join the Entire Discord.
Checkpoints are resolved in this order: