reflect
Reflect
Extract learnings from sessions and persist to skill files.
When to Reflect
Run /reflect after sessions with:
- Corrections - "actually use X", "no, do it this way"
- Discoveries - patterns that worked well
- Failures - approaches that didn't work
Usage
/reflect # Analyze current session, suggest skill updates
/reflect skill-name # Target specific skill for updates
More from spences10/claude-code-toolkit
terminal-optimization
Terminal setup for Claude Code. Use for Ghostty config, statusline customization, voice dictation, tmux worktrees.
17techdebt-finder
Find technical debt patterns in codebases. Use when asked to find duplicated code, inconsistent patterns, or refactoring opportunities.
9skill-creator
Design and create Claude Skills using progressive disclosure principles. Use when building new skills, planning skill architecture, or writing skill content.
6claude-md-maintenance
Maintain CLAUDE.md files effectively. Use when adding lessons learned, updating conventions, or restructuring project instructions.
5research
Verify sources before presenting findings. Use when asked to research links or documentation.
4plugin-dev
Validate, test, and distribute Claude Code plugins and marketplaces. Use when developing plugins, debugging validation errors, or preparing for distribution.
4