Generate weekly engineering retrospectives from git logs and analytics files.
npx skills add https://github.com/CarbeneAI/Forge --skill retro-carbeneai
Please help me install this Agent Skill. Skill: retro Source: https://github.com/CarbeneAI/Forge/tree/main/.claude/skills/retro Command: npx skills add https://github.com/CarbeneAI/Forge --skill retro-carbeneai
Engineering teams spend hours manually summarizing what shipped, who did what, and where quality or process gaps exist; retro automates that analysis so teams get a clear, data-driven retrospective in minutes rather than days.
Ask the assistant: /retro to generate a seven-day engineering retrospective for the current repository.
High-intent search queries and answers about installing and using this skill.
To generate an automated engineering retrospective, you can parse git commit history and engineering artifacts to produce a team-aware summary. This analysis outputs metrics, per-author breakdowns, commit histograms, and actionable recommendations for your repository.
Analyzing team code quality and contributor metrics involves parsing git logs and repository files to compute test LOC, hotspot churn, and PR size distribution. This produces per-author contributions, focus scores, and growth areas for a weekly engineering review.
Yes, you can run a retrospective analysis across a global cross-project window to summarize commits and sessions. It operates on multiple repositories to aggregate contributor breakdowns, backlog health, and engineering metrics into a unified report.
Tracking developer session patterns and commit distributions requires parsing git history to extract hourly distributions and session groupings. This yields commit histograms and developer-focused leaderboards to evaluate sprint velocity and focus.
Generating a git retrospective does not require external dependencies, but it operates using local gstack analytics files when available. It primarily parses git logs and repository files to compute quality signals and backlog health metrics.
You should use an automated retrospective when you need to summarize what shipped and identify process gaps quickly for an all-hands meeting. It replaces manual summarization by providing data-driven metrics, commit histograms, and team-aware recommendations in minutes.
KrismithReddy12Analyze engineering commit history and project timeline data to generate automated retrospective reports.
GenEducationAnalyze git commit history to generate weekly engineering retrospectives.
JaykaijackGenerate engineering retrospectives from git history and metrics.
yocxy2Analyze git commit history to generate engineering retrospectives.
