Generate engineering retrospective reports from commit history and work patterns.
npx skills add https://github.com/Manzueti/cyberdart --skill retro-manzueti
Please help me install this Agent Skill. Skill: retro Source: https://github.com/Manzueti/cyberdart/tree/main/retro Command: npx skills add https://github.com/Manzueti/cyberdart --skill retro-manzueti
This Skill automates the process of conducting weekly engineering retrospectives, analyzing commit history, work patterns, and code quality metrics with persistent history and trend tracking.
Run the retro skill to generate a weekly engineering retrospective report.
High-intent search queries and answers about installing and using this skill.
Automate engineering retrospectives by running a script that analyzes commit history and work patterns to generate weekly reports, tracking team contributions and identifying growth areas. You need access to commit history and project files.
Commit history analysis for tracking work patterns involves parsing commit logs to identify individual contributions, detect trends, and highlight areas for improvement. It provides persistent history tracking for weekly engineering reviews.
Yes, you can generate a weekly retrospective report that breaks down individual team contributions. The analysis highlights praise areas and specific growth opportunities per person based on their commit history.
Yes, you need access to both commit history and project files to analyze code quality metrics. This access allows the tool to evaluate work patterns and generate an accurate retrospective report for your sprint review.
Run an automated retrospective analysis at the end of a work week or sprint. This timing allows you to review the team's recent progress, assess code quality metrics, and identify areas for improvement before the next cycle.
Commit history analysis limitations include relying solely on commit data to evaluate contributions, which may miss pair programming or non-code work. It requires comprehensive project file access to accurately assess code quality metrics.
tsuna44Generate project-rulebook documentation from repository structure and git history.
KrismithReddy12Analyze engineering commit history and project timeline data to generate automated retrospective reports.
256javyAggregate commit history and code quality metrics into weekly engineering retrospectives.
mahg-esFacilitate structured sprint retrospectives and generate action plans.
