Analyze command history and commit logs to plan skill updates.
npx skills add https://github.com/kagenti/kagenti --skill skills-retrospective
Please help me install this Agent Skill. Skill: skills:retrospective Source: https://github.com/kagenti/kagenti/tree/main/.claude/skills/skills%3Aretrospective Command: npx skills add https://github.com/kagenti/kagenti --skill skills-retrospective
This Skill helps you systematically review your work sessions to identify inefficiencies, skill gaps, and areas for improvement, leading to more productive future sessions.
Run the retrospective skill to analyze the current session and identify areas for improvement.
High-intent search queries and answers about installing and using this skill.
To analyze command history for workflow inefficiencies, run an end-of-session retrospective. It examines command history, commit logs, and existing skill inventory to identify repeated commands and long debugging cycles, generating an actionable plan for skill refactoring.
A structured session retrospective for AI agent development is an end-of-session review that identifies skill gaps and refactoring opportunities. It analyzes observed patterns and commit history to document blind paths, suggesting new or updated skills for continuous improvement.
To identify skill gaps after a complex debugging session, analyze commit logs and command history for wasted iterations. This retrospective process documents what went wrong and generates a development plan to create or update skills that prevent similar issues.
Yes, you can check your existing skill inventory for duplicates or outdated structures. The retrospective analysis reviews your current skills alongside command history to detect inefficiencies and suggests actionable updates or refactoring opportunities.
The best way to document blind paths in commit logs is through a structured retrospective analysis. It identifies wasted iterations from your commit history and incorporates them into an actionable plan for skill development and maintenance to prevent future repeats.
You should run a workflow analysis at the end of a complex debugging session or development cycle. This retrospective review identifies frequent information lookups and long debugging cycles, generating actionable plans to update skills and address observed patterns.
cookysAnalyze Git history and sprint data to generate structured retrospective reports.
DethonAnalyze code quality to generate architectural improvement plans.
iani-kuliAnalyze agent skill files and generate diagnostic reports on trigger accuracy.
SakshamKandelAnalyze team progress from git commit history for weekly retrospectives.
