Analyze recent work across four dimensions and generate proposed documentation updates.
npx skills add https://github.com/dtinth/dotfiles --skill reflect-on-work
Please help me install this Agent Skill. Skill: reflect-on-work Source: https://github.com/dtinth/dotfiles/tree/main/claude/skills/reflect-on-work Command: npx skills add https://github.com/dtinth/dotfiles --skill reflect-on-work
This Skill automates a structured reflection process, ensuring valuable insights are captured and applied from your work. It prevents repeated mistakes and continuously improves your efficiency by systematically analyzing past actions and outcomes.
CLAUDE.md or project-specific documentation, ensuring learnings are codified.Reflect on the work we just completed on the user authentication module. What did we learn from the last coding session? Let's reflect on the recent refactoring of the payment gateway.
High-intent search queries and answers about installing and using this skill.
Structured work analysis evaluates four dimensions: what went well, what went wrong, what was confusing, and what knowledge is needed. This prevents repeated mistakes and captures actionable insights from completed features or focused sessions for continuous improvement.
Reflection is most valuable after completing a significant feature, wrapping up focused work, or when you need to identify what went well, what failed, and what knowledge would help future instances. It systematically extracts learnings before they fade.
After analyzing your work across the four reflection dimensions, the process generates proposed changes formatted for integration into project documentation like CLAUDE.md, ensuring learnings are codified and accessible for future reference.
The reflection process produces findings across what went well, what went wrong, what was confusing, and knowledge gaps, plus a separate list of proposed changes ready for your approval and documentation integration.
Yes. Reflection works after complex features, focused refactoring, coding sessions, or any significant work where you want to capture what went well, identify pain points, clarify confusion, and extract knowledge for future improvement.
quanganh208Summarize recent commits and session notes into Markdown journal entries.
tim099Log lessons learned from debugging and design errors to a JSONL file.
ReefBytes-OwnerCapture structured lessons learned into a local YAML knowledge base.
Soul-Brews-StudioCapture retrospective notes and generate concise lessons-learned summaries via /rrr alias.