By name: 707-name
description: "Name or rename the current session."
argument-hint:
allowed-tools: Bash(mkdir:), Bash(ls:), Bash(echo:), Bash(cat:), Bash(tee:*)
Canonical Paths
Before resolving any ShipFlow-owned file, load $SHIPFLOW_ROOT/skills/references/canonical-paths.md ($SHIPFLOW_ROOT defaults to $HOME/shipflow). ShipFlow tools, shared references, skill-local references/*, templates, workflow docs, and internal scripts must resolve from $SHIPFLOW_ROOT, not from the project repo where the skill is running. Project artifacts and source files still resolve from the current project root unless explicitly stated otherwise.
Chantier Tracking
Trace category: non-applicable.
Process role: helper.
This skill does not write to chantier specs. If invoked inside a spec-first flow, do not modify Skill Run History; include Chantier: non applicable or Chantier: non trace in the final report when useful, with the reason and the next lifecycle command if one is obvious.
Your task
Name the current session so it appears in the statusline and is saved for future reference.
The argument provided is: {{ args }}
Steps
Get the session name — use the argument if provided, otherwise ask the user with the runtime's structured question tool when available, or a concise plain-text question: "What name do you want to give this session?"
Find the current session ID — run:
ls -t ~/.claude/projects/*/*.jsonl 2>/dev/null | head -1 | xargs basename | sed 's/\.jsonl$//'Save the session name:
mkdir -p ~/.claude/session_notes echo "<name>" | tee ~/.claude/session_notes/<session_id>Confirm — tell the user the session is named and will appear in the statusline (📌
) after the next response.
Note
This is separate from Claude Code's built-in /rename command which renames the session in the UI sidebar.
Use /name to tag the session so the statusline always reminds you what you're working on.
You can use both: /rename for the sidebar, /name for the statusline.