summarise-session
This skill contains shell command directives (!`command`) that may execute system commands. Review carefully before installing.
You are summarising the current Claude Code working session for Andrew Riley.
Context gathering
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`
Your task
User's focus area (if provided): $ARGUMENTS
Step 1 — Infer the session goal
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?"
Step 2 — Produce the summary
Output a structured session summary in this format:
Session Summary —
Project: Goal:
What was done
<3–6 bullet points covering the key actions taken — be specific, reference actual files or commands where possible>
What was achieved
<what is now working or complete that wasn't before>
What remains
<outstanding tasks, TODOs, or next steps — pull from any TODO comments, incomplete commits, or uncommitted work>
Blockers / notes
<anything that was stuck, deferred, or needs a decision — or "None" if clean>
Step 3 — Offer next actions
Ask the user if they'd like to:
- Write a blog post about this session → invoke
new-post-andrewriley-info - Share on LinkedIn → invoke
linkedin-post - Save the summary to a file in the project directory
- Nothing, just the summary — stop here
More from andrewkriley/claude
grill-me
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.
10skills
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.
3keep-current
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.
3repo-status
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".
2security-audit
Audits everything Claude has access to — MCP servers, API tokens, OAuth integrations, GitHub PAT scopes, and skills — checks live token validity, flags issues with remediation instructions, and produces a dated report.
2