Analyze origin/main commits to compute activity, LOC changes, and contributor metrics.
npx skills add https://github.com/umairinayat/Specter-AI --skill retro-umairinayat
Please help me install this Agent Skill. Skill: retro Source: https://github.com/umairinayat/Specter-AI/tree/main/.claude/skills/retro Command: npx skills add https://github.com/umairinayat/Specter-AI --skill retro-umairinayat
Automates the generation of comprehensive engineering retrospectives by aggregating commit data, metrics, and team signals to reveal patterns, focus, and opportunities.
Run /retro to generate the current week's engineering retrospective using the default 7-day window
High-intent search queries and answers about installing and using this skill.
To generate an engineering retrospective, run the retro command to analyze the latest commits on origin/main. It computes overall activity, LOC changes, contributor counts, and per-author breakdowns to produce a structured narrative for your team.
An automated team retrospective includes commit-type distribution, hotspot files, session patterns, focus scores, and ship metrics. It also provides per-author insights and a team narrative interpreting the data to highlight trends and growth opportunities.
Yes, you can compare current engineering activity metrics with a previous retrospective. The output includes a comparison option if a prior retro exists, allowing you to track trends and identify shifts in contributor focus or LOC changes over time.
You can analyze contributor focus and work patterns by evaluating per-author breakdowns from your git history. The analysis surfaces top focus areas, work session patterns, and growth opportunities for each contributor based on their commit activity.
The retrospective analysis requires access to the origin/main branch to gather commit history and compute metrics. It analyzes the latest commits within a specified 7-day window by default to ensure consistent and accurate weekly reporting.
The best way to summarize weekly engineering team output is to aggregate commit data into a structured narrative. This approach highlights team wins, ship of the week, and concrete next steps, directly informing your weekly planning and resource allocation.
gewoonsebaRebase the current branch onto origin/main after conflict resolution.
14790897Analyze team resource capacity and workload distribution from project tracker data.
snewhouseConvert git commit history into weekly engineering retrospective metrics.
shekerkammaAutomates weekly engineering retrospective metrics from git commit history with configurable windows and saved snapshots.
