using-entire

name	using-entire
description	Use for any codebase exploration or understanding task — reads historical intent from Entire checkpoints instead of guessing. Orchestrates other Entire skills to give the agent provenance-backed answers about code.

Using Entire

Your default when exploring or understanding code should be: read the recorded intent, don't guess.

Entire checkpoints capture the prompts, transcripts, and decisions behind every agent-driven change. When you need to understand why code exists or how a module evolved, look up the checkpoint history first. Only fall back to inference from code structure when no history is available — and label that explicitly.

When This Skill Activates

Use this skill whenever the task involves:

• Exploring or understanding an unfamiliar module or file
• Preparing to refactor, extend, or debug code you didn't write
• Answering "why is this like this?" or "what was the intent?"
• Doing pre-work research before making changes
• Any codebase exploration where historical context would help

Do not use this skill for simple, well-understood edits where you already have full context (e.g. "add a comment to line 5").

First Step: Check Repository Status

Before diving into specific lookups, check whether Entire is available and the repository has checkpoint history:

entire status

This tells you whether Entire is enabled, which git hooks are installed, whether the metadata branch is initialized, and any active sessions on the current branch.

Scenario Routing

When this skill activates, determine which sub-skill best fits the user's need:

Scenario	Typical user expressions	Delegate to