Wrap up the active session: resolve its registered notes.md, summarise what this session did (Decisions, Files touched, Open questions, Next steps), update those sections, and append a Session history entry. If Obsidian is enabled in config, distils a short atomic note to the matching vault. Trigger on "/close-session", "wrap up", "save session notes", "ferme la session".
Two modes. (1) No arg โ wraps the current session via /close-session logic, verifies notes.md was saved (persistence gate), then prints fresh-start options. (2) With <session-slug> โ loads an existing notes.md into the CURRENT fresh session, checks out the branch from its frontmatter, registers this session in active-sessions.json, and suggests a /rename. Trigger on "/restart-session", "/restart-session <slug>", "resume <slug>", "reprendre la session".
Checkpoint the active session WITHOUT closing it: resolve its registered notes.md, summarise what this session did so far (Decisions, Files touched, Open questions, Next steps), update those sections, and append an "(in progress)" Session history entry. The session stays open. Useful mid-session, or right before context compaction. Trigger on "/save-session", "save session", "checkpoint", "sauvegarde la session".
Open a new session: creates a workspace + notes.md under the category's configured folder, registers it in ~/.claude/active-sessions.json, syncs the git repo, and renames the session. Categories & note locations come from your config. Aborts if the workspace already exists (use /restart-session instead). Trigger on "/start-session", "start a session", "/start-session FEAT PROJ-123 short-name".
Safely rename a session category EVERYWHERE โ moves its folder, re-tags every notes.md frontmatter, updates active-sessions.json, and renames it in the shared config. The dashboard app is read-only and only changes the config (which orphans old sessions); this skill is the writer that actually migrates references. Trigger on "/rename-category <OLD> <NEW>", "rename category <X> to <Y>", "renomme la catรฉgorie <X> en <Y>".
Adopt the CURRENT (already-running) Claude Code session into management: writes a notes.md under a category's configured folder and registers the session in ~/.claude/active-sessions.json, so the dashboard tracks it like a /start-ed one. Meant to run right after `claude --resume <id>` (the dashboard's +Import does this for you). Unlike /start-session it does NOT create a fresh workspace or sync a repo โ it binds the session you're already in. Trigger on "/import-session", "/import-session FEAT name".
Archive a stale session without loading its context โ stamps its notes.md as "archived" in the Session history and removes it from active-sessions.json. The note file is kept on disk. Use for sessions that are done or abandoned. Trigger on "/archive-session <slug>", "archive session <slug>".