← ClaudeAtlas

notelisted

Append a timestamped mid-session note to the session journal — finding/decision/summary tags for across-compaction memory. Use when you discover something the session must remember past /compact. Folded to the handoff at session end.
tansuasici/claude-code-kit · ★ 1 · AI & Automation · score 77
Install: claude install-skill tansuasici/claude-code-kit
# Note ## Core Rule Append `<ISO8601> [<tag>] <text>` to `.hook-state/session-journal.md`. Tag MUST be one of `finding`, `decision`, `summary`. The journal is transient (gitignored, same lifetime as other `.hook-state/*`) but durable across `/compact` within the same session. ## Process ```bash scripts/note.sh <tag> <text> ``` The helper validates the tag, ensures the `.hook-state/` dir + `.gitignore` exist, appends a timestamped line, and prints a confirmation with the new entry count. ## Tags Three only — pick exactly one per note. Don't invent new tags; extend the vocabulary only after a recurring pattern shows up across multiple sessions. | Tag | Use for | |---|---| | `finding` | A non-obvious technical observation worth carrying past `/compact` (e.g. "qdrant treats null filter as ANY") | | `decision` | A choice made mid-session that may later become an ADR in `tasks/decisions.md` (e.g. "going with Drizzle over Prisma") | | `summary` | A "what state are we in right now" checkpoint, useful before a tool-heavy block (e.g. "auth wired, billing endpoints next") | The lifecycle differs by tag: - `finding` / `decision` → folded into `tasks/handoff-<session-id>.md` at session end (durable) - `summary` → discarded at session end if no findings/decisions are present (transient breadcrumb) ## When to Use When you discover something that: - The session needs to remember after `/compact` (compaction wipes mid-session findings from the conversation) - Doesn't yet warrant