Analyze commit history and artifacts to generate structured retrospective reports.
npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill retro-shaheerkhawaja
Please help me install this Agent Skill. Skill: retro Source: https://github.com/ShaheerKhawaja/ProductionOS/tree/main/skills/retro Command: npx skills add https://github.com/ShaheerKhawaja/ProductionOS --skill retro-shaheerkhawaja
Summarizes recent work across code changes to reveal patterns, outcomes, and actionable improvements to inform process and product enhancements.
Review the last sprint's activity to generate a concise retrospective with concrete improvements.
High-intent search queries and answers about installing and using this skill.
To generate a sprint retrospective from commit history, you can apply automated analysis across recent codebase work to summarize outcomes, failures, and improvement opportunities. This process reads commit artifacts and outputs a structured retrospective report with suggested follow-ups.
Yes, you can analyze codebase patterns to surface repeated pain points after a release. This retrospective analysis reads recent commits and artifacts to identify development patterns, summarizing outcomes and generating concrete improvement actions for your team.
The best way to summarize shipped work and create actionable backlog items is through automated retrospective analysis. It reads recent codebase changes to reveal patterns and outcomes, outputting a concise retrospective report with suggested follow-ups and concrete improvements.
Yes, this retrospective analysis supports optional alignment with specific time windows or scopes for focused reviews. You can target specific deployment cycles, releases, or sprints to generate a concise retrospective tailored to that activity period.
No, you do not need any external dependencies to analyze codebase artifacts for improvement opportunities. The retrospective analysis operates independently to read commit history and output a structured report with actionable follow-up items.
Automated codebase retrospective tools differ from manual review by reading commit history to objectively surface patterns and repeated pain points. They generate a structured retrospective report with concrete improvement actions, reducing manual effort and uncovering hidden development trends.
alangebPerform Git bisecting, cherry-picking, and log analysis operations locally.
GDSDNCreate prioritized, tagged QA follow-up items linked to project backlog stories.
memorysaverAutomate the dispatch-launch-monitor-review-wrap-dispatch cycle in CI/CD pipelines.
shakhovskiya-createReview sprint outcomes across architecture, code quality, tests, and performance.
