Analyze Git commit history and code quality metrics to generate team-aware retrospective narratives.
npx skills add https://github.com/Batsirai/adoro-studios --skill retro-batsirai
Please help me install this Agent Skill. Skill: retro Source: https://github.com/Batsirai/adoro-studios/tree/main/Skills/retro Command: npx skills add https://github.com/Batsirai/adoro-studios --skill retro-batsirai
Weekly engineering retrospectives that analyze commit history, work patterns, and code quality metrics, with persistent history and per-person growth insights.
Tell the AI to generate a weekly retro for the current sprint using the repository history.
High-intent search queries and answers about installing and using this skill.
To generate a weekly retrospective from Git commit history, you need to grant the AI repository access so it can analyze work patterns and code quality metrics to produce a structured narrative and actionable improvements.
You can review what your team shipped by analyzing code quality metrics and work patterns to generate a team-aware retrospective that provides per-person praise and growth opportunities based on individual contributions.
A narrative-driven retrospective surfaces actionable improvements by tracking contribution trends across sprints and combining Git commit data with code quality metrics to output a structured narrative for team review.
Yes, you need repository access to analyze work patterns and generate a team-aware retrospective because the process relies on reading Git commit history and code quality metrics to provide per-person growth insights.
The best way to track engineering trends across multiple sprints is to use a history-aware retrospective tool that analyzes Git commit data to maintain persistent history and surface actionable improvements over time.
A limitation when generating per-person growth insights from PR cycles is that the analysis relies entirely on available Git commit history and code quality metrics, requiring consistent repository access to accurately surface actionable improvements.
KrismithReddy12Analyze git commit history to generate engineering retrospectives and team performance metrics.
makyua-sanAnalyze commit history and code quality metrics to generate weekly retrospectives.
ericdahl-devGenerate weekly engineering retrospectives from git commit history and code quality metrics.
louisfghbvcAnalyze commit history and code quality metrics to summarize engineering activity.
