session
Use at session boundaries — resume at the start of a new session (resolve a scoped handoff and brief on where to pick up), handoff at the end of a session (write it), checkpoint for a mid-session save without the full ceremony, or name to label the session. Also use to look back at recorded sessions — list, show, timeline, or recurring tool failures. Replaces /session-handoff, /session-resume, /name-session.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- session
- description
- Use at session boundaries — resume at the start of a new session (resolve a scoped handoff and brief on where to pick up), handoff at the end of a session (write it), checkpoint for a mid-session save without the full ceremony, or name to label the session. Also use to look back at recorded sessions — list, show, timeline, or recurring tool failures. Replaces /session-handoff, /session-resume, /name-session.
- allowed-tools
- Bash(git status *), Bash(git branch *), Bash(git log *), Bash(git rev-parse *), Bash(git stash *), Bash(git worktree *), Bash(git check-ignore *), Bash(gh pr view *), Bash(gh pr list *), Bash(ls *), Bash(wc *), Bash(date *), Bash(grep *), Bash(stat *), Bash(mv *), Bash(mkdir *), Read, Write, Edit, Glob
- argument-hint
- [handoff|resume|name|checkpoint|list|show|timeline|failures] [--auto]
- user-invocable
- true
02 资源文件 6
- 参考文档checkpoint.md3.7 KB
- 参考文档handoff.md7.4 KB
- 参考文档history.md2.4 KB
- 参考文档name.md4.6 KB
- 参考文档resume.md8.7 KB
- 参考文档templates.md3.8 KB
03 SKILL.md 正文
Session
Codex: Read
../_shared/codex-tools.mdbefore following this skill. Apply its tool, root and dispatch mappings throughout.
One engine for session continuity — handoff, resume, name, and checkpoint as verb modes. Continuity is owned by the native session at R/sessions/<native-sid>/handoff.md; scoped pointers in R/continuity/ discover prior handoffs and separately published artifacts. Session continuity only — durable knowledge capture is /claudna:capture territory.
Mode dispatch
Arguments to dispatch (first token = verb, the rest belong to the verb): $ARGUMENTS
| Verb | When | Auto | Depth |
|---|---|---|---|
resume |
Start of a new session — read the handoff, reap, scan live state, brief | yes | resume.md |
handoff |
End of a session — capture, reap, write the handoff | yes | handoff.md |
checkpoint |
Mid-session save — append new items, no reaping, no ceremony | yes | checkpoint.md |
name |
Label the session for /resume discovery |
no | name.md |
list, show, timeline, failures |
Look back at what the session store recorded: past sessions, one session's events, recurring tool failures | yes | history.md |
For the selected verb, read ONLY its depth file in this skill directory and follow it exactly — never load another verb's depth.
templates.md is the one exception, because it is not a verb depth: it holds the v2 content format, reaper rules, migration notes, and narrow source-level stable surface. Load it alongside the verb's depth file whenever a verb reads or writes continuity.
No verb token → deterministic inference only (F2, epic #165), rules checked in order — first match wins:
- Fresh session (little prior conversation) and a unique scoped handoff resolves →
resume(checked first: the read-only mode wins any tie). - The request contains an explicit wrap-up cue — one of: "wrap up", "wrapping up", "done for the day", "end of session", "handoff", "sign off", "calling it" →
handoff. - Anything else → print the table above and stop. Never infer
checkpointorname, and never ask a blocking question — the table is the answer. - Headless /
--auto: the verb is required — never inferred.--autoon thenameverb emits the structured result with"outcome": "blocked"and ablocker_descriptionnaming it interactive-only (it hands the user a/renamecommand).
Shared conventions
- Identity: use the actual native SID and host from a qualified host surface. Never derive one from cwd, time, or an operation ID. Missing or conflicting identity means no continuity write.
- Ownership: write only
R/sessions/<current-native-sid>/handoff.md; predecessors remain immutable. Resolve scoped pointers without selecting “latest”. - CLI:
session-storebelow is shorthand forpython3 -B "<loaded-package>/lib/claudna/session_store"; append the documented verb and arguments to that executable. Followdocumentation/guides/STORAGE_OWNERSHIP.mdfor the effective root and ownership contract. - Permissions: use the host's ordinary command and destination permission controls for that exact loaded helper. The frontmatter grants no generic Python pre-approval. If permission is denied or unavailable, report partial persistence with
handoff_path: null; retain existing content and never change global grants or substitute another writer. Native interactive and--autopermission acceptance remain separate qualification gates. - Atomic writes: submit the complete v2 content to
session-store handoff-write; do not create shell temp files or usemv. - Capture-off:
CLAUDNA_SESSION_STORE=0disables background checkpointing. An explicit user-requested manual handoff may still persist with verified native identity; it does not initialize lifecycle state. Artifact-only cross-session discovery requires explicit public-context opt-in. - No compound commands: separate parallel tool calls;
allowed-toolspatterns match simple commands only. --autois silent: no questions, reaper as the only pruning mechanism, and a §10.C structured result (per../_shared/orchestration-guide.md) as the final output —"skill": "session"with"mode"insideartifacts.- Speed over thoroughness: resume under 30 seconds; handoff under 60 with
--auto; checkpoint faster than both.
04 同仓库更多 Skills
example-review
Use when you want to review pull requests with detailed, actionable feedback on code quality, correctness, and maintainability.
bad-skill
Too short
worktree
Use when starting feature work that needs isolation from the current workspace, or when running multiple Claude sessions in parallel on different branches — creates and manages git worktrees. For fetching latest main into every existing worktree and branch across your sibling repos, use /claudna:sync-branches instead.
weigh-development-paths
Use when at a development junction with multiple viable approaches — architecture choices, refactoring strategies, where to put new code, or which pattern to follow. Triggers on 'which approach', 'how should I', 'Option A vs B', or any point where the next step isn't obvious and the wrong choice creates rework.
verify-completion
Use when about to claim work is complete, fixed, or passing -- requires running verification commands and confirming output before making any success claims.
vercel
Use for Vercel operations — deploy to production or preview (or roll back), view, filter, or debug deployment logs, or check project status (deployments, domains, env vars, config). Replaces /vercel-deploy, /vercel-logs, /vercel-status.