Analyze git diffs and logs to codify session learnings into actionable artifacts.
npx skills add https://github.com/phrazzld/agent-skills --skill done-phrazzld
Please help me install this Agent Skill. Skill: done Source: https://github.com/phrazzld/agent-skills/tree/main/core/done Command: npx skills add https://github.com/phrazzld/agent-skills --skill done-phrazzld
This Skill addresses the challenge of capturing and acting upon learnings from development sessions, ensuring that valuable insights are not lost and are instead used to improve future work.
/done to document the root cause, the fix, and any new patterns discovered, ensuring the team doesn't repeat the same mistake.Run the done skill to capture learnings from the last coding session.
High-intent search queries and answers about installing and using this skill.
To capture development learnings, you can run a structured session retrospective that analyzes git diffs and logs. This process categorizes findings into predefined buckets and systematically codifies them into actionable artifacts like updated documentation or new hooks.
The best way to document root causes is using a retrospective workflow that identifies friction points and bugs. It codifies these insights into updated documentation, new hooks, or agent configurations to prevent the team from repeating the same mistake.
You create a feedback loop by capturing implementation feedback directly from your session retrospective and git logs. This feedback is then routed to GitHub issues to inform future planning and workflow improvement.
Yes, you can codify session insights into hooks and agent configurations. The retrospective process takes categorized findings from your git history and systematically writes them into relevant files like memory, documentation, or agent settings.
Session retrospective codification works without external dependencies. It relies solely on internal scripts and reference components to analyze your local git diffs and logs, categorize the findings, and generate actionable artifacts.
goffityAnalyze git changes to generate retrospective drafts with Before/After context.
ikeisukeCollect user feedback and create a draft GitHub Issue for review.
GrassHopper42Generate weekly engineering retrospective reports from git commit history and code quality metrics.
FrancisVargaAnalyze retrospective sessions to extract actionable learnings and generate rules and KG entries.