ReddRadar
Agent skill
session-review
Analyzes the current session to extract patterns, preferences, and learnings. Use when running session retrospectives, debriefs, post-mortems, or reflecting on insights worth remembering. Produces structured reviews capturing what worked, what to improve, and actionable takeaways.
Install this agent skill to your Project
npx add-skill https://github.com/philoserf/claude-code-setup/tree/main/skills/session-review
SKILL.md
Session Review
Comprehensive session analysis to build cumulative knowledge across interactions.
Objective
Extract reusable insights from the session that make future sessions more effective. Focus on patterns, not just facts.
When to Use
- After significant debugging or problem-solving sessions
- When you've learned something important about the codebase
- After discovering user preferences through trial and error
- When system relationships became clearer through investigation
When NOT to Use
- Short, straightforward sessions with no corrections or surprises
- When the user just wants a quick task done, not a retrospective
- Use
md-improveinstead if the only goal is updating CLAUDE.md
Analysis Dimensions
| Dimension | Focus |
|---|---|
| Problems & Solutions | Symptoms, root causes, dead ends, key insights |
| Code Patterns | Design patterns, naming, data flow, error handling |
| User Preferences | Explicit and implicit preferences across tools/style/process |
| System Understanding | Components, dependencies, failure modes |
| Knowledge Gaps | Misunderstandings, missing info, better approaches |
See analysis-dimensions.md for the full framework with questions, formats, and examples.
Process
- Review - Walk through the session conversation
- Extract - Identify insights in each dimension
- Synthesize - Connect related learnings
- Document - Create structured reflection
- Act - Generate concrete deliverables
- Save - Write the review to Obsidian (see below)
Deliverables
Based on the analysis, generate applicable items:
- CLAUDE.md updates - Preferences and patterns to remember
- Code comments - System understanding to preserve
- Documentation - Workflows or processes to document
- Future considerations - Things to address in later sessions
- Obsidian note - Every session review is saved to the vault
Obsidian Storage
After presenting the review, save it to Obsidian using the obsidian CLI (invoke the obsidian-cli skill for reference):
obsidian create path="Session Reviews/YYYY-MM-DD <short description>.md" content="<review content>" silent
- Title:
# Session Review: <short description> - Date and repo/project as metadata at the top
- Use the same markdown content shown to the user
- Do not ask for confirmation — just save it
Verification
- Review covers all 5 dimensions (or explicitly notes "N/A" for dimensions with no findings)
- Each insight is grounded in a specific conversation moment, not hypothetical
- CLAUDE.md updates are diffed before applying
- Obsidian note was saved successfully (confirm with
obsidian read)
Guidelines
- Focus on reusable patterns, not session-specific facts
- Capture the "why" behind decisions, not just the "what"
- Preserve user voice when documenting preferences
- Prioritize insights by impact on future effectiveness
- Build cumulative knowledge, not just session notes
Reference Files
- analysis-dimensions.md — Full 5-dimension framework with questions, formats, and examples
- output-templates.md — Full and compact reflection formats
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
philoserf/claude-code-setup
pre-release
Validates a project is ready to tag and ship. Use when tagging a release, cutting a version, shipping a package, or asking "are we ready to release?" Checks repo hygiene, CI status, docs, version sync, and build verification. Optimized for Obsidian plugins with fallback detection for other project types.
philoserf/claude-code-setup
local-issues
Reviews a codebase for bugs, design issues, and code cleanliness problems with specific file paths and line numbers. Use when auditing code quality, finding bugs, doing a code review, finding problems, or reviewing a project for issues. Creates issue files in `.issues/` directory.
philoserf/claude-code-setup
skill-improve
Generates prioritized improvement recommendations for Claude Code skills. Use when improving skills, enhancing customizations, or wanting actionable feedback on how to make a skill better. Provides impact/effort prioritization with specific fix suggestions.
philoserf/claude-code-setup
release
Executes the final release workflow for Obsidian plugins after pre-release checks pass. Use when tagging a release, publishing a version, or shipping an Obsidian plugin. Bumps version via bun run script, creates git tag, pushes to trigger GitHub Actions, and updates GitHub release notes from CHANGELOG.md.
philoserf/claude-code-setup
skill-quality
Scores Claude Code skills (1-5) across 6 weighted quality dimensions aligned with official Anthropic docs. Use when evaluating skill quality, rating skills, scoring customizations, comparing skill effectiveness, or checking if a skill follows best practices. Produces per-dimension scores with evidence, weighted totals, quality tier classification, and actionable improvement recommendations.
philoserf/claude-code-setup
obsidian-cli
Interacts with Obsidian vaults using the Obsidian CLI to read, create, and manage notes, tasks, properties, tags, and more. Also supports plugin and theme development with commands to reload plugins, run JavaScript, capture errors, take screenshots, and inspect the DOM. Use when the user asks to interact with their Obsidian vault, manage notes, add to daily note, find notes about a topic, check tasks, append to a note, query the vault, list tags, list files, manage bookmarks, check sync status, view file history, use templates, query bases, run QuickAdd, perform vault operations from the command line, or develop and debug Obsidian plugins and themes.
Didn't find tool you were looking for?