context-keeper
Write one immutable snapshot for the current working session. Reconcile living docs later with doc-keeper, or with tiger-doc-keeper for Tiger Claw.
Codex Runtime
- Dependencies: bash; Codex rollout/session storage
bashCodex rollout/session storage- Execution: Operate directly in the main Codex agent.
- Resolve
SKILL_DIR from the directory containing this loaded SKILL.md.
- Never print, log, or expose secret values.
Inputs and Preflight
- Confirm
bash is available and the selected Codex rollout/session storage can be created or written without changing an existing snapshot. If any mandatory dependency is unavailable, stop before writing and report the missing command or storage path.
- Resolve the target repository with
git rev-parse --show-toplevel; use the current directory only when it is not a Git repository.
- Set
SESSION_DIR to an explicitly supplied CONTEXT_KEEPER_DIR, otherwise to <repo-root>/.codex/sessions.
- Review this session's decisions, discoveries, diffs, commits, test output, deployments, and live checks. Treat unsupported claims as unverified.
- Query the next path without writing:
CONTEXT_KEEPER_DIR="$SESSION_DIR" bash "$SKILL_DIR/scripts/new-session.sh" --path
- Stop if that path already exists. Never choose an older file to edit.
Procedure
- Summarize the session arc in one to three evidence-grounded lines.
- Scaffold exactly one new snapshot, always passing the Codex target explicitly:
CONTEXT_KEEPER_DIR="$SESSION_DIR" bash "$SKILL_DIR/scripts/new-session.sh" "<session arc>"
- Open only the newly created file and complete its five sections:
- Decisions, including ruled-out options.
- Discoveries grounded in observed evidence.
- Shipped or changed work with PRs, SHAs, UTC timestamps, and live proof where applicable.
- Verified versus unverified claims, naming every verification gap.
- Open threads and one concrete next step.
- Re-read the new snapshot against the session evidence. Downgrade any unsupported statement to unverified.
- Report the new path. Leave living-doc reconciliation to the appropriate sibling skill.
Safety and Errors
- Write only beneath the selected
.codex/sessions/ directory.
- Append by creating one new file; never edit a prior snapshot. Put corrections in the new snapshot's Discoveries section.
- Do not change code, dashboard docs, timeless-rule docs, or memory files.
- If the scaffold script fails, the target exists, or evidence is incomplete, stop and report the exact condition without claiming a snapshot was completed.
Output Contract
Return the created snapshot path, its session number, the evidence used for verified claims, every unverified gap, and the single next action. Do not claim completion unless the new file exists and prior snapshots remain untouched.
1---2name: context-keeper3description: Write the append-only per-session flight recorder to the CURRENT project's .codex/sessions/ — a dated, numbered snapshot of what THIS session decided, discovered, shipped, verified (vs not), and the next step. Project-agnostic — works for any project; defaults to the current git repo root (override with CONTEXT_KEEPER_DIR). Records the session (the raw record); a separate docs-reconcile step then updates the project's living docs. Use at session close before reconciling docs, or when Brent says "context keeper", "save the session", "write the flight recorder", "snapshot this session", "record the session". Append-only — one new file per session, never edits prior snapshots, never overclaims.4---56# context-keeper78Write one immutable snapshot for the current working session. Reconcile living docs later with `doc-keeper`, or with `tiger-doc-keeper` for Tiger Claw.910## Codex Runtime1112- **Dependencies:** bash; Codex rollout/session storage13- `bash`14- `Codex rollout/session storage`15- **Execution:** Operate directly in the main Codex agent.16- Resolve `SKILL_DIR` from the directory containing this loaded `SKILL.md`.17- Never print, log, or expose secret values.1819## Inputs and Preflight20211. Confirm `bash` is available and the selected Codex rollout/session storage can be created or written without changing an existing snapshot. If any mandatory dependency is unavailable, stop before writing and report the missing command or storage path.222. Resolve the target repository with `git rev-parse --show-toplevel`; use the current directory only when it is not a Git repository.233. Set `SESSION_DIR` to an explicitly supplied `CONTEXT_KEEPER_DIR`, otherwise to `<repo-root>/.codex/sessions`.244. Review this session's decisions, discoveries, diffs, commits, test output, deployments, and live checks. Treat unsupported claims as unverified.255. Query the next path without writing:26 ```bash27 CONTEXT_KEEPER_DIR="$SESSION_DIR" bash "$SKILL_DIR/scripts/new-session.sh" --path28 ```296. Stop if that path already exists. Never choose an older file to edit.3031## Procedure32331. Summarize the session arc in one to three evidence-grounded lines.342. Scaffold exactly one new snapshot, always passing the Codex target explicitly:35 ```bash36 CONTEXT_KEEPER_DIR="$SESSION_DIR" bash "$SKILL_DIR/scripts/new-session.sh" "<session arc>"37 ```383. Open only the newly created file and complete its five sections:39 - Decisions, including ruled-out options.40 - Discoveries grounded in observed evidence.41 - Shipped or changed work with PRs, SHAs, UTC timestamps, and live proof where applicable.42 - Verified versus unverified claims, naming every verification gap.43 - Open threads and one concrete next step.444. Re-read the new snapshot against the session evidence. Downgrade any unsupported statement to unverified.455. Report the new path. Leave living-doc reconciliation to the appropriate sibling skill.4647## Safety and Errors4849- Write only beneath the selected `.codex/sessions/` directory.50- Append by creating one new file; never edit a prior snapshot. Put corrections in the new snapshot's Discoveries section.51- Do not change code, dashboard docs, timeless-rule docs, or memory files.52- If the scaffold script fails, the target exists, or evidence is incomplete, stop and report the exact condition without claiming a snapshot was completed.5354## Output Contract5556Return the created snapshot path, its session number, the evidence used for verified claims, every unverified gap, and the single next action. Do not claim completion unless the new file exists and prior snapshots remain untouched.
bbrysonelite-max