Generates engineering retrospective reports from git commit history and time-windowed analysis.
npx skills add https://github.com/alexaundre/mycc --skill retro-alexaundre
Please help me install this Agent Skill. Skill: retro Source: https://github.com/alexaundre/mycc/tree/main/.claude/skills/retro Command: npx skills add https://github.com/alexaundre/mycc --skill retro-alexaundre
It automates the laborious process of reading through git history to surface work rhythm, code-quality signals, hotspots, and actionable improvement suggestions so developers and teams can iterate faster without manual aggregation.
Use retro to analyze the last 7 days of git commits and generate a concise engineering retrospective report.
High-intent search queries and answers about installing and using this skill.
Generate an engineering retrospective by analyzing recent commits within a specific time window to automatically surface work rhythm, code-quality signals, hotspot files, and context durability metrics for developer self-review.
To identify technical debt hotspots from git commit metrics, you need to track files most frequently modified and areas with repeated fixes, which indicate accumulating code-quality issues and architectural drift.
Yes, you can analyze git commit history using time-windowed scenarios such as 24h, 7d, 14d, 30d, or explicit date ranges to produce concise retrospective reports tailored to your sprint or review cycle.
Commit-type distribution measures work rhythm and code quality by categorizing commits into feat, fix, refactor, and docs, revealing fix density, revert frequency, and commit message quality signals for the analyzed period.
Context durability assessment in git repository analysis evaluates long-session drift and the presence of archival or trajectory artifacts within task logs to ensure development context is preserved across sessions.
Automated git commit analysis for sprint reviews relies entirely on commit metadata and message quality; it cannot capture uncommitted work, external blockers, or offline design discussions not reflected in the repository history.
CarbeneAIGenerate weekly engineering retrospectives from git logs and analytics files.
gmh5225Analyze git commit history within a time range to generate a 7-dimension retrospective report.
KrismithReddy12Calculate a weighted 0-10 code quality score from linters and test runners.
AbyssCNAnalyze git history to generate engineering retrospective reports.
