/chronicle
Write the session log — alias for /session-log during the grace window through 2026-10-31. Renamed per ADR-040 Decision 1. Both names resolve to the same behavior; after grace ends, only /session-log resolves.
/chronicle/chronicle defaultType it bare, or paste it with loose context after — Claude figures out the rest.
Grace-window sessions still call for /chronicle. New alias for /session-log keeps both live.
Writes the session log through the grace window. Same output as /session-log.
Takes in
- Optional session or goal ref
Returns
- Session log entry at chronicle/*
What it does
/chronicle is the old name for /session-log. It still works during the grace window through 2026-10-31 per ADR-031 and .claude/rules/we-dont-break-adopters.md. Both names produce the same session log entry with the same shape and the same Gate Evidence table.
The rename is per ADR-040 Decision 1 (planning-skill vocabulary rewrite). "Chronicle" was borrowed from Ryan Singer's Shape Up; "session log" reads plain per Krug and Cooper consultations documented at ADR-040.
Read the full skill
The complete instructions live at .claude/skills/chronicle/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.
Where in the SDLC
Why this phase: Write the session log — alias for /session-log during the grace window through 2026-10-31 per ADR-040. Both names resolve to the same behavior.
Related
- Skills catalog — browse all skills grouped by lifecycle phase
- Tier system — what each tier gives you
FAQ
Terms from bassclef vocabulary that appear on this page.
- chronicle
- A narrative log of what a session shipped — what worked, what did not, what got deferred. Written at session-end. Bassclef's chronicles live under `docs/chronicles/YYYY-MM-DD-slug.md`. Chronicles are how future sessions understand context that the code alone cannot show. See: /docs/skills/session-log
- hook
- A shell script bassclef wires into Claude Code's tool-invocation lifecycle. Hooks fire at events like PreToolUse (before an Edit lands) or SessionStart (when a session opens). Hooks enforce rules mechanically — a rule says 'don't do X'; a hook fires and BLOCKs if X happens.
- rule
- A markdown file auto-loaded into every session's context. Rules pin discipline the agent applies to every response (plain-English writing, blocked-items protocol, temperance gates). Different from a hook — rules are steering; hooks are enforcement.
- skill
- A user-invocable command (like `/kiss` or `/temperance`) that runs a specific bassclef workflow. Every skill lives at `.claude/skills/<name>/SKILL.md` with frontmatter + procedure. Adopters type the slash command; Claude Code loads the skill and runs it.
- adopter
- A repo that has bassclef installed — either via `bassclef init` (lite tier from npm) or via the symlink pattern (standard tier with an Anthropic key). Bassclef's discipline: never break adopters. Every change to a downstream-observable surface ships with a compat shim.
- session log
- Same shape as a chronicle — narrative record of what a session shipped. `/session-log` skill drafts it from the session's commits + branch state. Feeds into `/journal` when the operator wants an audience-tuned draft. See: /docs/skills/session-log
Shipped by @kingofrock · Read the essays
/ticket
Compose well-formed product tickets — INVEST for stories, modified-INVEST for epics (V + N only). Adopter-mode cross-posts to bassclef with the adopter-source label. Standard-tier — pending audit at bassclef-web#193.
/clean-artifacts
Sweep workflow exhaust from the repo (stale verify markers, old Playwright screenshots, expired SDLC traces). Strict allowlist; never touches git-tracked files or critical artifacts. Dry-run by default. Runs standalone or via /session-end.