entireio
- 18 skills
- 0 followers
- 6 hours ago last updated
- ▌ Stats · entireioReport how much this repo's coding-agent sessions used the entire-graph code graph versus grep/read exploration, and the estimated tokens that saved. Use when the user asks "how much did the graph save", "token savings", "graph usage", "am I actually using the graph", or invokes /entire-graph:stats. Read-only, local, no network.
- ▌
- ▌ Entire External Agent · entireio bundleRun all three external agent binary phases sequentially: research, write-tests, and implement using black-box-first TDD across protocol compliance, lifecycle integration, and unit tests. Accepts an optional argument to run a single phase: research, write-tests, or implement.
- ▌ Agent Integration · entireio bundleRun all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent support", or wants to run the full agent integration pipeline end-to-end.
- ▌ E2e · entireio bundleOrchestrate E2E test triage and fix implementation: runs triage-ci then implement sequentially. Accepts test names, --agent, artifact path, or CI run reference. For individual phases, use /e2e:triage-ci, /e2e:debug, or /e2e:implement. Use when the user says "triage e2e", "fix e2e failures", or wants the full triage-to-fix pipeline.
- ▌ Changelog · entireioGenerate or update the CHANGELOG.md for a new release version. Use when the user says "generate changelog", "update changelog", "write release notes", or asks to prepare a changelog for a version like "changelog for 0.5.3".
- ▌ Test Repo · entireio bundleUse this skill to test strategy changes against a fresh test repository. Invoke when the user asks to "test against a test repo", "validate the changes", or wants to verify session hooks, commits, and checkpoint creation work correctly.
- ▌ Explain · entireioExplains 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.
- ▌ Using Entire · entireioUse as the FIRST action on any research, investigation, or codebase-understanding request — "research X", "investigate X", "look into X", "dig into X", "search X", "explore X", "understand X", "why is this like this" — before Glob, Grep, or Read. Recorded intent lives in Entire checkpoints on the server, not in local files, so an empty or unfamiliar working copy is not a reason to skip it. Routes to the right Entire sub-skill (search, recall, explain, what-happened, replay, teach, review, session-handoff).
- ▌ What Happened · entireioExplain 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 checkpoint 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.
- ▌ Session Handoff · entireioUse 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
- ▌ Address Findings · entireioAddress the review findings posted on an Entire trail: fetch the trail's open findings, fix the code, and resolve them on the trail. Use when the user gives a trail URL or number and asks to address, fix, or resolve its findings or review comments. Not for local diff review — that is the `review` skill.
- ▌ Session To Skill · entireioUse when the user wants to turn one or more Entire-tracked sessions, checkpoints, or repeated agent workflows into a reusable agent skill.
- ▌ Session Crosslink · entireioUse 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.
- ▌ Teach · entireioUse 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"
- ▌ Recall · entireioUse 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"
- ▌ Replay · entireioUse 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"
- ▌ Review · entireio bundleReview code changes on the current branch using checkpoint transcript context to understand developer intent before auditing the diff. Use when the user asks for a code review, wants to review branch changes, or asks to audit recent work before merging.