Jason Stedwell
be3fd36ebf
1. capture-update keeps the whole body (was truncating to first line) 2. frontmatter completeness: kind-default status + kind-seeded tags at capture, fm create-or-replace, incomplete-frontmatter lint, sweep backfill (one data source: KIND_STATUS/KIND_REQUIRED_FM) 3. pre-write duplicate gate (exit 76, --merge-into/--force) 4. recall corpus + ranking: sessions/journal indexed (down-weighted), BM25 x freshness x status fusion, recall --json, index schema 2 5. session hooks: SessionStart auto-load, Stop reflection nudge 6. one-tap triage verb with processing-log audit; --json on read verbs +22 mock end-to-end tests; all suites green. Docs current (README, CHANGELOG, SKILL.md, commands, references, MAINTENANCE, eval README). Drops tracked .DS_Store (gitignored); retires README-gretchen.md (moved to gitignored dist/); adds the field report that drove item 2. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2.0 KiB
2.0 KiB
description, argument-hint
| description | argument-hint |
|---|---|
| Reflect on this session — extract durable memories and propose them for one-tap capture | [optional focus, e.g. 'just decisions'] |
Use the echo-memory skill to run session reflection (H5). Scan this conversation for things worth remembering across sessions, then propose them — don't write blindly.
- Extract durable items from the conversation: new facts, preferences, decisions,
commitments, people/companies/projects introduced, and anything the operator said to remember.
Skip the ephemeral. Anchor relative dates on the conversation's
currentDate. - Emit a JSON array of proposals (one per item), each:
{"title","kind","body","aliases","tags","sources","confidence"}—kind∈person, company, concept, reference, meeting, project, area, semantic, episodic, working, skill, decision; set"inbox": truewhen the home is genuinely unknown;confidence0–1 (items below 0.6 are dropped — send those to the inbox instead). Write the array to a file with the Write tool (cross-platform; no heredoc). - Preview, then apply. Dry-run first (writes nothing) and show the operator the plan; only apply after they confirm.
ECHO="${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/echo.py" # python3 (Windows: python / py -3)
[ -f "$ECHO" ] || ECHO=$(ls /sessions/*/mnt/.remote-plugins/*/skills/echo-memory/scripts/echo.py 2>/dev/null | head -1) # CoWork sandbox fallback
python3 "$ECHO" reflect proposals.json # dry-run: validate + classify + preview
python3 "$ECHO" reflect proposals.json --apply # write — routes each via capture (indexed, linked, logged)
reflect dedups every proposal against the entity index (so it shows create-vs-update),
skips below-confidence items, and routes inbox proposals to the capture inbox. Each
applied item goes through the normal capture path — canonical frontmatter, auto-linking,
and the recall index — and the writes are lock-guarded. $ARGUMENTS