Analyze commit history and team activity to generate engineering retrospectives.
npx skills add https://github.com/shaneholloman/ship --skill retro-shaneholloman
Please help me install this Agent Skill. Skill: retro Source: https://github.com/shaneholloman/ship/tree/main/retro Command: npx skills add https://github.com/shaneholloman/ship --skill retro-shaneholloman
Analyze commit history and team activity to produce a comprehensive engineering retrospective with per-person praise and growth opportunities.
Run /retro to generate a weekly retrospective for the default 7-day window and see a narrative report.
High-intent search queries and answers about installing and using this skill.
Generate a team retrospective by analyzing git commit history to produce a comprehensive report of team activity. The retrospective covers commits, LOC, PRs, test health, hotspot analysis, and per-author breakdowns for the specified period.
A code quality retrospective includes metrics-driven narratives with per-author breakdowns, focus scores, and trend comparisons. It collects commits, LOC, test health, hotspot analysis, and session patterns to identify individual contributions and growth areas.
Yes, you can compare engineering metrics retrospectives over time using comparison mode. The system persists history, allowing you to save retrospectives and compare team-wide focus scores, trends, and per-author contributions across different periods.
Retrospective analysis supports weekly sprints and any period up to 30 days. You can adjust the default 7-day window to analyze longer team activity cycles, capturing commit history and engineering metrics for the entire duration.
The best way to analyze individual developer contributions is generating a team-aware retrospective that parses git history. It provides per-author breakdowns, highlighting individual contributions and suggesting growth opportunities within the metrics-driven narrative.
The commit history window for a team-wide retrospective is limited to a maximum of 30 days. For the default weekly sprint, the system analyzes a 7-day window; exceeding the 30-day limit requires breaking the analysis into smaller periods.
CarbeneAIGenerate weekly engineering retrospectives from git logs and analytics files.
abnejsolutions-altAnalyze controls, evidence, and findings to produce compliance dashboards and reports.
timurgaleevAnalyze git history and code quality signals to generate engineering retrospectives.
nocnocgroupAggregate commits, PRs, and test activity into team retrospectives.
