name-session

Name session — propose a conventional session name

Build a <scope>-<descriptive> name from the current context and emit the active client's ready-to-paste rename command.

Important — client command and limitation

• It cannot rename the session for you. Slash commands emitted in model output are inert text; the user must enter the command in the client's command input.
• Pi: use /name {session-name}. Never suggest /rename or /settings name in Pi.
• Claude Code: use /rename {session-name}.
• If the client is unknown, state both commands rather than guessing.

Convention

<scope>-<descriptive>

• scope — the most specific identifier available, in priority order:
  1. Jira ticket from the branch name (e.g. AB-1505) — keep its natural Jira case.
  2. Active bead ID (e.g. bd-123) if no ticket.
  3. PR number (e.g. pr-6563) if neither.
  4. Omit the scope entirely if none apply — just use the descriptive part.
• descriptive — kebab-case, ≤4 words, the most specific noun phrase for what this session is doing. rebase-pr-status beats git-stuff. Derive it from the conversation, not the branch (the branch already gives the scope).

Examples: AB-1505-rebase-pr-status, bd-412-flaky-test-hunt, pr-6563-review-comments, auth0-logout-investigation.

Instructions

1. Gather scope signals (parallel)

git rev-parse --abbrev-ref HEAD
bd list --status=in_progress 2>/dev/null

• Extract a Jira ticket from the branch by matching /[A-Z]+-\d+/.
• If no ticket and exactly one bead is in progress, use its ID.
• If neither and there's an obvious PR in play this session, run gh pr view --json number,title to grab the number. Don't fetch a PR speculatively — only if the session is clearly about one.

Fail soft: any missing signal just drops to the next priority. Not in a git repo → skip straight to a descriptive-only name.

2. Derive the descriptive half

From the current conversation, pick the ≤4-word kebab phrase that best names what this session is for. Prefer the concrete task over the topic — rebase-pr-status over maintenance. If the session genuinely spans several unrelated things, name the dominant one; don't try to cram them all in.