Fix skill names · Entire
Fix skill names
bb722d9→main
alishakawaguchi·3mo ago·10 files·+34 added/-377 removed
Sessions
6cfb81c05ca9 View transcript
Changes
10
- .entire
- M.gitignore +2/-1
- logs
- Dentire.log
- A.gitignore +1
- MREADME.md +31/-2
- docs/plans
- D2026-04-10-gemini-packaging-design.md -70
- D2026-04-10-gemini-packaging-implementation.md -162
- D2026-04-10-readme-install-marketplaces-design.md -54
- plugins/entire/skills
- search
- MSKILL.md -1
- session-handoff
- MSKILL.md -1
- search
1
2
3
4
4
5
tmp/
settings.local.json
metadata/
logs/
current_session
logs/
No newline at end of file
M.entire/.gitignore +2/-1
1
No renderable diff hunks available.
D.entire/logs/entire.log
1
docs
No newline at end of file
A.gitignore +1
18 unmodified lines
# Install docs and manifests per agent platform
## First Skill: `session-handoff`
### Skills
`session-handoff` reads Entire session metadata and helps move work from one agent to another without making the user reconstruct the context manually.
#### Current behavior:
- resolves checkpoints from: local `entire/checkpoints/v1` branch, `.entire/settings.json` `checkpoint_remote`, or nearby local clone
- filters sessions by agent name (e.g. "codex", "gemini") when mentioned
### `explain`
Traces source code back to the original conversation where it was created. Use `/explain` with a function, file, or line of code to understand _why_ it exists.
#### Current behavior:
- identifies the commit that introduced the code via git blame/log
- reads the session transcript via `entire explain --no-pager --commit <sha>`
- works with functions, files, and individual line changes
- reports clearly when code is untracked, uncommitted, or created outside an Entire session
### `search`
Searches Entire checkpoint history and transcripts to find prior work by topic, repo, branch, author, or time window.
#### Current behavior:
- runs `entire search "<query>" --json` and summarizes the top matches
- supports filters: `--repo`, `--branch`, `--author`, `--date`, and inline query filters like `author:<name>`, `date:week`
- drills into a specific result with `entire explain --checkpoint <id> --full --no-pager`
- broadens searches progressively when initial results are empty (remove branch filter, widen date, simplify terms)
## Installation
Install the agent that matches your workflow from its marketplace, manifest, or install-doc entrypoint:
### Checkpoint Resolution
MREADME.md +31/-2
```bash
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
# Gemini Packaging Design
**Date:** 2026-04-10
## Goal
Make this repository's Gemini integration match the upstream `obra/superpowers` pattern by exposing a root-level `gemini-extension.json` manifest and a root-level `GEMINI.md` entrypoint, while removing the legacy Gemini-specific install document.
## Current State
- Gemini support is currently documented only through [`.gemini/INSTALL.md`](/Users/alisha/Projects/agent-plugins/.gemini/INSTALL.md).
- Other agent integrations already use package or manifest-style entrypoints at predictable locations.
- Upstream Superpowers exposes Gemini through:
- root `gemini-extension.json`
- root `GEMINI.md`
## Chosen Approach
Adopt the upstream root-level manifest approach directly.
### Files to add
- `gemini-extension.json`
- `GEMINI.md`
### Files to update
- `README.md`
### Files to remove
- `.gemini/INSTALL.md`
## Design Details
### `gemini-extension.json`
Create a root manifest shaped like the upstream file:
- `name`
- `description`
- `version`
- `contextFileName`
The values should use this repository's metadata, with `contextFileName` set to `GEMINI.md`.
### `GEMINI.md`
Create a root Gemini entrypoint that points Gemini at this repo's skill bootstrap path. Since this repo does not mirror Superpowers' `skills/using-superpowers` tree, the file should reference the actual local skill entrypoint:
- `@./plugins/entire/skills/session-handoff/SKILL.md`
This keeps the Gemini experience aligned with the upstream packaging model while remaining correct for this repository's structure.
### README changes
Update the Gemini installation guidance so it no longer points to `.gemini/INSTALL.md`. The README should describe Gemini as using the root-level manifest and entrypoint, consistent with the Superpowers layout.
## Non-Goals
- No changes to the `session-handoff` skill behavior.
- No changes to Codex, Claude, Cursor, or OpenCode packaging.
- No attempt to preserve the old `.gemini/INSTALL.md` flow.
## Verification
- Confirm `gemini-extension.json` exists at the repository root.
- Confirm `GEMINI.md` exists at the repository root.
- Confirm `README.md` no longer references `.gemini/INSTALL.md`.
- Confirm `.gemini/INSTALL.md` has been removed.