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