Name Session
Derive a conventional session name from the branch ticket, active bead, open PR, and current work, then print the paste-ready rename command for the active client. Use when a session's auto-name is generic.
Install
npx skills add flurdy/agent-skills --skill name-sessiongit clone --depth 1 https://github.com/flurdy/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/name-session ~/.claude/skills/name-sessionPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# 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
Harness selection comes from the current tool surface.
Never use the shell, PATH, filesystem, process list, or installed binaries to detect another client.
Treat the client as unknown when that surface does not conclusively identify Pi or Claude Code.
These rules are shared with `/wrap-up` and `/handoffs`; command printing is a proposal, not execution.
- 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.Details
- Skill name
name-session- Repository
- flurdy/agent-skills
- Path
skills/name-session/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Name Session skill do?
Derive a conventional session name from the branch ticket, active bead, open PR, and current work, then print the paste-ready rename command for the active client. Use when a session's auto-name is generic.
How do I install the Name Session skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add flurdy/agent-skills --skill name-session. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Name Session popular?
It lives in flurdy/agent-skills, which has 9 GitHub stars and 0 forks.
Related skills
Architect
9flurdy/agent-skills
Architecture and implementation planning gate for complex or high-blast-radius work. Produces evidence-backed decisions, reviewable slices, acceptance evidence, and conditional human review ownership without editing code.
Artifact Hygiene
9flurdy/agent-skills
Run a local-only, read-only advisory audit of publishable working-tree files and unpublished branch history with redaction-safe findings.
Backlog Groom
9flurdy/agent-skills
Auto-detects workspace unfinished backlogs across unique stores; otherwise local open beads. Flags thin prose, missing labels, drift, lifecycle and duplicates. Report-only; mutations need approval, destructive ones individually.
PR Review Requests
9flurdy/agent-skills
Show a read-only inbound PR dashboard with request/update times, exact-head CI, merge state, your and others reviews, feedback, and manual next steps.
Jira Ticket
9flurdy/agent-skills
Look up Jira ticket details including summary, type, and description. Use this to fetch ticket context for branch naming, PR creation, or understanding requirements.
PR Reviewers
9flurdy/agent-skills
Recommend GitHub reviewers from the authenticated user's previous PRs in one repository, adding labelled sibling-workspace evidence filtered to people with target access. Read-only; never requests reviews.
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.