claude-session-skill 1.1.7 → 1.1.8

package/README.md

@@ -1,5 +1,8 @@
 # claude-session-skill
 
+[![npm version](https://img.shields.io/npm/v/claude-session-skill)](https://www.npmjs.com/package/claude-session-skill)
+[![license](https://img.shields.io/github/license/ITeachYouAI/claude-session-skill)](LICENSE)
+
 A [Claude Code](https://docs.anthropic.com/en/docs/claude-code) skill for searching, browsing, and naming past sessions. Indexes all session history and generates AI summaries so you can find any session by keyword, project, or name.
 
 This package ships two ways to use the same session index:
@@ -32,6 +35,7 @@ Claude Code discovers the skill automatically via `SKILL.md` triggers. Open any
 /session show <id>               # Show full session details (partial IDs work)
 /session name <name>             # Name the most recent session
 /session name <id> <name>        # Name a specific session by ID
+/session autoname [<id>]         # Generate title from summary + session start time
 /session unname [<id>]           # Clear a session's name
 /session search <query>          # Search by keyword
 /session <query>                 # Shorthand for search
@@ -48,8 +52,12 @@ Session naming is handled via natural language — you never type or see session
 | "Name this session `<name>`" | Names the most recent session |
 | "Name the session where I did `<thing>`" | Claude searches, finds it, names it |
 | After `/session list`: "name the second one `<name>`" | Claude uses the ID from the list output |
+| "Name + summarize that one" | Claude runs `autoname` and creates a timestamped title |
 | "Unname the `<name>` session" | Claude searches, finds it, clears the name |
 
+When Claude auto-generates a title from the session summary, the title is prefixed with the
+session start time in `dd/mm/yy HH:MM` format, for example `31/03/26 03:18 Infra fix`.
+
 Names are 1–50 characters. Named sessions rank highest in search results. Clearing a name with `unname` preserves the AI summary.
 
 ## How it works
@@ -138,6 +146,7 @@ Or with the global install:
 | `search_sessions` | `query: string` | Search by keyword or quoted phrase |
 | `show_session` | `id: string` | Detailed view of a specific session |
 | `name_session` | `id?: string, name: string` | Assign a memorable name to a session |
+| `autoname_session` | `id?: string` | Generate a timestamped title from the session summary |
 | `unname_session` | `id?: string` | Remove a session's name |
 | `session_stats` | — | Statistics broken down by project |
 
@@ -151,7 +160,7 @@ bunx @modelcontextprotocol/inspector bun mcp-server.ts
 
 ```
 session.ts              # CLI entry point
-mcp-server.ts           # MCP server entry point (6 tools)
+mcp-server.ts           # MCP server entry point (7 tools)
 lib/
   indexer.ts            # Index builder, summarizer, name persistence
   search.ts             # Weighted keyword search

package/SKILL.md

@@ -26,6 +26,7 @@ triggers:
 /session show <id>               # Full details (supports partial IDs)
 /session name <name>             # Name the most recent session (by last activity)
 /session name <id> <name>        # Name a specific session by ID
+/session autoname [<id>]         # Generate title from summary + session start time
 /session unname [<id>]           # Clear a session's name
 /session rebuild                 # Force rebuild the index
 /session stats                   # Index statistics by project
@@ -51,6 +52,15 @@ Entry point: `bun run ~/.claude/skills/session/session.ts <command> [args]`
 3. **Do NOT ask follow-up questions** after `list` or `search`. The output is self-contained.
 4. **If the user references an already-shown list** (e.g., "the most recent", "the third one", "that one") — use the IDs already printed in the previous output. Do NOT re-run `list` or `show` unnecessarily.
 
+### Name + summarize requests
+
+If the user asks you to **"name + summarize"** a session, or otherwise wants a generated title based on the session itself:
+
+1. Use `session.ts autoname [<id>]` instead of asking them for a manual title.
+2. The generated session name MUST start with the session start timestamp in this exact format: `dd/mm/yy HH:MM`
+3. The rest of the title should be a concise summary derived from the session's summary or first bullet.
+4. Keep the final title within the existing 50-character limit.
+
 ### Naming Sessions
 
 Users name sessions in natural language. They will NEVER type IDs. Your job is to resolve which session they mean.
@@ -62,10 +72,12 @@ Users name sessions in natural language. They will NEVER type IDs. Your job is t
 3. **"Name my last session X"** — Run: `session.ts name "<name>"` (defaults to most recent by last activity)
 4. **After `/session list`**, user says **"name the third one X"** — You already have the list output with IDs. Use the ID from the third entry.
 5. **"Clear the name from X"** / **"Unname the clinic bot session"** — Search to find it, then run: `session.ts unname <id>`. Or `session.ts unname` to clear the most recent.
+6. **"Name + summarize this session"** / **"Summarize and title that one"** — Run: `session.ts autoname` (or `session.ts autoname <id>` if the target session is already known)
 
 **Key rules:**
 - The user NEVER types or sees session IDs. You handle all ID resolution behind the scenes.
 - Names are 1-50 characters. If the user gives something longer, ask them to shorten it.
+- Auto-generated names for name+summarize requests MUST include the session start time prefix in `dd/mm/yy HH:MM` format.
 - Named sessions show as `Name — summary` in list view and `Name: X` in detail view.
 - Names are searchable — `/session search "Vault Reorg"` finds named sessions with highest relevance.
 - Names can be cleared with `unname` — this removes the name but preserves the AI summary.