Egregore Wrap
Native Codex Egregore skill. Use this inside an Egregore checkout with
bin/agent.sh. The command routes through bin/capture-run.sh --mode personal.
It writes the personal record first, appends graph and handoff-completion events
to the local WAL, and reconciles them detached; do not wait for or repeat that
background work.
Flow
- Synthesize a topic, a one to three sentence summary, and concise open notes
from the current session.
- If the session has ambiguous or potentially misleading state, confirm with
the user. Use structured Codex question tooling when available; otherwise
show numbered choices plus
Other: and wait.
- Resolve the author from
.egregore-state.json github_username, then
name, then git config.
- Write the notes to a temp markdown file.
- Run:
bin/agent.sh wrap --from "$AUTHOR" --topic "$TOPIC" --summary "$SUMMARY" --body-file "$BODY_FILE"
- If
git status --porcelain reports repo changes after the wrap, run:
bin/agent.sh save --message "Wrap: $TOPIC" --topic "$TOPIC"
- Report the
memory/wraps/... path and whether code changes were saved.
Output
Structured UX parity is required. Finish with the standard Egregore wrap
confirmation TUI, not a prose-only summary:
- Use a 72-column outer box with only the four standard line patterns:
top rule, separator rule, content line, bottom rule.
- Header:
WRAP, author, and date.
- Body: topic, one compact summary, open threads or "No open threads", and
the
memory/wraps/... path.
- Footer: saved/pushed status. If code changes were saved, show that. If the
wrap only touched memory, say so.
- Output the box directly, preferably in a
text fenced block, with no
narration before it.
Rules
- Do not use Claude Code commands.
- Do not invent finished work. Separate completed work, verification, and open
follow-ups.
- If save fails, report the failure and leave the local commits untouched.
1---2name: wrap3description: Wrap an Egregore session when the user invokes /wrap or $wrap, or says they are done, wrapping up, or at a stopping point in Codex.4---56# Egregore Wrap78Native Codex Egregore skill. Use this inside an Egregore checkout with9`bin/agent.sh`. The command routes through `bin/capture-run.sh --mode personal`.10It writes the personal record first, appends graph and handoff-completion events11to the local WAL, and reconciles them detached; do not wait for or repeat that12background work.1314## Flow15161. Synthesize a topic, a one to three sentence summary, and concise open notes17 from the current session.182. If the session has ambiguous or potentially misleading state, confirm with19 the user. Use structured Codex question tooling when available; otherwise20 show numbered choices plus `Other:` and wait.213. Resolve the author from `.egregore-state.json` `github_username`, then22 `name`, then git config.234. Write the notes to a temp markdown file.245. Run:2526```bash27bin/agent.sh wrap --from "$AUTHOR" --topic "$TOPIC" --summary "$SUMMARY" --body-file "$BODY_FILE"28```29306. If `git status --porcelain` reports repo changes after the wrap, run:3132```bash33bin/agent.sh save --message "Wrap: $TOPIC" --topic "$TOPIC"34```35367. Report the `memory/wraps/...` path and whether code changes were saved.3738## Output3940Structured UX parity is required. Finish with the standard Egregore wrap41confirmation TUI, not a prose-only summary:4243- Use a 72-column outer box with only the four standard line patterns:44 top rule, separator rule, content line, bottom rule.45- Header: `WRAP`, author, and date.46- Body: topic, one compact summary, open threads or "No open threads", and47 the `memory/wraps/...` path.48- Footer: saved/pushed status. If code changes were saved, show that. If the49 wrap only touched memory, say so.50- Output the box directly, preferably in a `text` fenced block, with no51 narration before it.5253## Rules5455- Do not use Claude Code commands.56- Do not invent finished work. Separate completed work, verification, and open57 follow-ups.58- If save fails, report the failure and leave the local commits untouched.
egregore-labs