Stats
Actions
Tags
From session
Show a lightweight check of the current work context. Use when the user asks "what was I working on?", "do I have a session?", "session status", or comes back after a break and wants a reminder.
How this skill is triggered — by the user, by Claude, or both
Slash command
/session:statusThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Lightweight check of the current work context.
Lightweight check of the current work context.
Run catchup:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/catchup
From the output, extract and present a concise status card:
Branch: <branch>
Commits ahead of <default>: <N>
Linked issue: #N — <title> (if branch matches type/NNN-*)
Uncommitted changes: <none | N files>
Recent commits: <last 3 subjects>
If the branch matches type/NNN-*, fetch just the issue title (no full body):
bash ${CLAUDE_PLUGIN_ROOT}/scripts/git-cli issue show <N> | jq -r '"#\(.number) — \(.title) [\(.state)]"'
Do not read changed files or rebuild context. This is intentionally lightweight. Point the user to /session:resume or /session:catchup for full context.
npx claudepluginhub st0nefish/agent-toolkit --plugin sessionSummarizes git repository state: branch/sync status, staged/unstaged/untracked changes counts, recent commits, stashes, and suggested next steps.
CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.
Analyzes git commits since base branch, file changes, uncommitted work, and optional Linear ticket to summarize branch intent and status for resuming development.