Summarize git activity into weekly per-person metrics for retrospectives.
npx skills add https://github.com/joi-fairshare/agentic-workflow --skill weeklyretro
Please help me install this Agent Skill. Skill: weeklyRetro Source: https://github.com/joi-fairshare/agentic-workflow/tree/main/skills/weeklyRetro Command: npx skills add https://github.com/joi-fairshare/agentic-workflow --skill weeklyretro
Weekly retrospectives rarely capture the full git history context, so teams struggle to quantify individual contributions, streaks, and current test health without manual log parsing and report writing.
Run /weeklyRetro to analyze the past week's commits and surface shipping streaks.
High-intent search queries and answers about installing and using this skill.
To generate a weekly retrospective report from git history, run /weeklyRetro to aggregate per-person commits, lines changed, streaks, and test health into a structured markdown file saved in the repository retros directory.
Yes, you can track individual contributor metrics from git logs by analyzing consecutive commit days to compute current and longest shipping streaks, alongside per-person commits and lines changed for the selected period.
To quantify test health for weekly git activity, the system executes the project test suite and diffs newly added tests against the baseline, surfacing pass rates and new test coverage within the retrospective report.
The best way to identify high-churn files and ownership gaps is to aggregate git activity per contributor, highlighting which files change most frequently and which directories lack clear ownership to guide next-week team focus.
Yes, weekly git reporting works with conventional commit types by parsing commit messages to categorize each contributor's activity, providing structured team insights for the selected retrospective period.
To filter git metrics for specific team members during a retrospective, apply the analysis to selected contributors, computing individual commits, top directories, and shipping streaks only for those filtered users.
hamzaPixlGenerate engineering retrospective reports from git repository history.
JeremiahEllingtonAnalyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.
zebbernGenerate unit and integration tests from git diffs and project conventions.
himes19Generate a weekly retrospective report with developer stats, shipping streaks, and test health trends.
