Menú
Summarises the current working session — what was worked on, what was achieved, what remains, and any blockers. Use at the end of a session or when handing off work.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Interview the user relentlessly about a plan, idea, or project until a shared understanding is reached. Walks down each branch of the design tree, resolving dependencies between decisions one-by-one. Use when starting something new or when a plan needs rigorous thinking-through.
Draft and publish a LinkedIn post on behalf of the user. Use when the user wants to share something on LinkedIn — a project, an insight, a win, a lesson learned, or a reaction to something in the industry.
Lists all available Claude Code skills with descriptions and usage hints. Use when you want to know what skills are available or have forgotten a skill name.
Sends a short session update message to a Webex room. Searches for the room by name, confirms with the user, then posts a concise paragraph summarising what was worked on. Use at the end of a coding session to share progress with a team or channel.
Audits README.md, CLAUDE.md, and PROFILE.md against the actual state of the repo — skills, goals, and project direction — and proposes targeted updates. Also infers PROFILE.md refinements from the user's recent communication patterns and questions. Run periodically to keep docs in sync with the project.
Checks the sync status of a git repository — local vs remote branches, commits ahead/behind, open PRs, and working tree state. Works across any project. Use when the user asks "what's the status of the repo", "are local and remote in sync", "check the branches", or "what's the state of dev and main".
| name | summarise-session |
| description | Summarises the current working session — what was worked on, what was achieved, what remains, and any blockers. Use at the end of a session or when handing off work. |
| argument-hint | [{"optional":"project name or focus area"}] |
You are summarising the current Claude Code working session.
Current directory and git status:
!`pwd`
!`git status --short 2>/dev/null`
Recent commits:
!`git log --oneline -15 2>/dev/null`
Files changed (staged and unstaged):
!`git diff --name-only 2>/dev/null`
!`git diff --name-only --cached 2>/dev/null`
Current date/time:
!`date`
User's focus area (if provided): $ARGUMENTS
From the git history and changed files, determine what this session was primarily about. If $ARGUMENTS is provided, use that as context.
If the goal is unclear from context alone, ask the user one question: "What were you trying to achieve in this session?"
Output a structured session summary in this format:
Project: Goal:
<3–6 bullet points covering the key actions taken — be specific, reference actual files or commands where possible>
<what is now working or complete that wasn't before>
<outstanding tasks, TODOs, or next steps — pull from any TODO comments, incomplete commits, or uncommitted work>
<anything that was stuck, deferred, or needs a decision — or "None" if clean>
Ask the user if they'd like to:
/new-post-andrewriley-info from the ~/dev/www-andrewriley-info projectlinkedin-post