Analyze feature development cycles using Git history and codebase metrics.
npx skills add https://github.com/enpuyou/sed.i --skill retro-enpuyou
Please help me install this Agent Skill. Skill: retro Source: https://github.com/enpuyou/sed.i/tree/main/.claude/skills/retro Command: npx skills add https://github.com/enpuyou/sed.i --skill retro-enpuyou
This Skill facilitates a structured post-mortem analysis of feature development, identifying successes, areas for improvement, and actionable takeaways.
Invoke the retro skill to analyze the current branch's feature development.
High-intent search queries and answers about installing and using this skill.
Post-mortem analysis of feature development uses Git history and commit analysis to assess decision-making and quality outcomes, producing actionable recommendations for process improvement. It evaluates codebase metrics to pinpoint strengths and weaknesses after deployment.
Analyzing feature completions for process and quality improvements involves evaluating technical outcomes and process effectiveness. This structured review assesses development cycles to identify successes, areas for improvement, and actionable takeaways for future refinement.
Yes, Git commit analysis evaluates codebase metrics to support a feature retrospective. It assesses process effectiveness and quality outcomes by reviewing development history, which helps generate actionable recommendations for refining future feature development.
A structured retrospective is needed after a feature deployment to evaluate process effectiveness and quality outcomes. It performs an in-depth review of the development cycle to identify areas of strength and potential weaknesses, yielding actionable takeaways for process refinement.
Post-mortem analysis to assess decision-making in feature development requires no specific dependencies. It utilizes Git history and codebase metrics to evaluate quality outcomes and process effectiveness, directly generating actionable recommendations for improvement.
Codebase metrics for feature development quality assessment rely on Git history and commit analysis. While they effectively evaluate process effectiveness and technical outcomes to produce actionable insights, they are limited to historical data and do not predict future development anomalies.
cookysAnalyze Git history and sprint data to generate structured retrospective reports.
HirogaKatageriAnalyze project trackers and generate structured progress reports with blockers and recommendations.
michsindlingerAutomate code quality tracking and reporting across CI/CD pipelines.
hieutrtrAutomate incident response planning and post-mortem documentation for Python/React applications.
