entire-query

Query a repository's AI session history (Entire checkpoints, sessions, transcripts) via the `eq` CLI to answer questions about why code was written a certain way, what alternatives were explored, when and by which agent something was added, how many tokens a feature consumed, how much of a file was AI-generated, what tools or skills were used, and how to reproduce a past session. Use when the user asks about implementation history, intent, reasoning, prior work, AI/agent attribution, token cost, skill-firing audits, Bash command audits, or session reproduction in a repository that uses Entire (https://entire.io). Trigger words include "why", "how come", "when", "who", "history", "intent", "rationale", "previously", "past", "cost", "tokens", "attribution", "agent-written", "skill firing", and the equivalent terms in the user's language. Skip when the question is about current code behavior, future plans, or pure Git operations unrelated to AI sessions.

Build CLI applications with Rune, a TypeScript-first, agent-friendly CLI framework that uses file-based command routing. Use this skill when the user is creating, modifying, or testing CLI commands with Rune, or scaffolding a new Rune project with create-rune-app.