Analyze git history to generate engineering retrospectives with shipping trends and code quality signals.
npx skills add https://github.com/linenoize/topia --skill retro-linenoize
Please help me install this Agent Skill. Skill: retro Source: https://github.com/linenoize/topia/tree/main/skills/retro Command: npx skills add https://github.com/linenoize/topia --skill retro-linenoize
This Skill turns raw git activity into a clear engineering retrospective so teams can understand what shipped, how work is trending, and where quality or focus is slipping.
Ask the assistant to run a seven-day engineering retro for the current repository and return a concise report with metrics, hotspots, trends, and next-step habits.
High-intent search queries and answers about installing and using this skill.
To generate an engineering retrospective from git history, you parse commit data to analyze shipping trends, code quality signals, and team work patterns. This produces a structured report covering metrics, hotspots, and actionable habits for your next sprint or weekly review.
Code churn hotspots are files with frequent changes or fix-heavy activity that need refactoring. You detect them through commit analysis by parsing git history to identify high-churn areas and missing test coverage, revealing where code quality is slipping.
Yes, you can compare current git commit trends with previous sprint reviews using compare-mode analysis. The process tracks shipping streaks and saves structured JSON snapshots from prior retros, allowing you to measure performance shifts and long-term work pattern trends.
Yes, this git retrospective analysis works across repositories with one or more contributors. It measures individual commits, active days, and hourly activity to reveal team work patterns, making it suitable for both solo projects and collaborative engineering teams.
You track team work patterns and active days from git commits by parsing commit history and grouping related activity into sessions. This analysis measures hourly activity and contributor engagement to reveal how the engineering team actually works over weekly or monthly periods.
The best way to run a weekly code quality retrospective is to analyze a seven-day window of git history to extract fix-heavy periods, churn hotspots, and missing test coverage. This generates a candid report with metrics, risks, and concrete habits for the next week.
gth-aiAnalyze git commit history and code metrics to generate engineering retrospectives.
anserIndicusCompare community sentiment and topic popularity across time periods.
farmountainDetect code smells and apply incremental refactorings with test coverage.
esopianAnalyzes git commit history to generate weekly engineering retrospective reports.
