Entire

Using using-superpowers and writing-skills for this edit. I’m opening the skill guidance and the current plugins/entire/skills/search/SKILL.md first so I can fill it in consistently with the repo’s existing skill patterns.

The target file is empty. I’m checking the neighboring entire skills and plugin metadata now so the new skill matches the existing voice, trigger descriptions, and any tool assumptions.

I have enough context to draft this cleanly. Next I’m pulling the repo README and any references to a search workflow so the new skill reflects the intended Entire CLI usage rather than inventing behavior.

There’s no existing search-skill text in the repo, so I need to define it from the actual CLI surface instead of copying a pattern. I’m checking whether the local entire CLI exposes a search command and what flags it supports before I write the skill.

I’ve confirmed the local CLI behavior: entire search is a checkpoint search command with JSON output, filters, paging, and an auth requirement. I’m drafting the skill around that exact surface now, with concise trigger text and concrete fallbacks instead of speculative workflow.

Before I edit, I’m checking the plugin manifests once so the new file’s frontmatter and naming don’t conflict with how this package is exposed. After that I’ll patch search/SKILL.md directly.

I’m editing plugins/entire/skills/search/SKILL.md now. The new content will stay tight: trigger-focused frontmatter, exact entire search usage, auth/install fallbacks, and a clear handoff from search results to entire explain when the user wants deeper context.

The skill body is in place. I’m doing a quick verification pass now to make sure the file reads cleanly and that the commands and fallbacks match the local entire CLI surface I checked earlier.

I’ve verified the rendered skill text. Before I close this out, I’m checking the repo state under the verification-before-completion workflow so I can report exactly what changed and whether there’s anything else to flag.

Filled out SKILL.md with a concrete entire search workflow: trigger-focused frontmatter, exact CLI usage with --json and filters, when to switch to session-handoff, how to inspect a hit via entire explain --checkpoint, and install/auth/no-results fallbacks.

Verification: I checked the file contents after editing and confirmed the documented command surface against the local CLI (entire version, entire search --help). git status --short shows this file is currently untracked: ?? plugins/entire/skills/search/SKILL.md.

Using verification-before-completion for the commit step. I’m checking the repo state and the exact change first, then I’ll stage only this new skill file and create a focused commit message.

The worktree has unrelated changes in README.md and .entire/logs/entire.log. I’m staging only SKILL.md, checking the staged diff, and committing that file alone.

The staged file is the intended search-skill content. I’m verifying exactly what is staged and then creating a single-file commit with a narrow message.

The commit is created. I’m doing one last status check so I can report the exact commit and confirm only the unrelated pre-existing changes remain unstaged.

The commit succeeded, but the worktree is still dirty, including a fresh unstaged change in SKILL.md. I’m checking that diff so I can tell you exactly what the commit contains versus what remains local.

Committed as 900b1aa with message Add Entire search skill.

The worktree is still dirty after the commit. git status --short shows unstaged changes in .entire/logs/entire.log, README.md, plugins/entire/skills/search/SKILL.md, and plugins/entire/skills/session-handoff/SKILL.md. For search/SKILL.md, the current unstaged diff removes the name: search frontmatter line, so the commit contains the version with name: search, but the working tree no longer does.