Compiles weekly engineering retrospectives from git history and code-quality metrics.
npx skills add https://github.com/mr-daedalium/ostack --skill retro-mr-daedalium
Please help me install this Agent Skill. Skill: retro Source: https://github.com/mr-daedalium/ostack/tree/main/retro Command: npx skills add https://github.com/mr-daedalium/ostack --skill retro-mr-daedalium
Weekly retrospectives are hard to compile from raw git history and code metrics. This Skill analyzes commit history, work patterns, and code quality metrics to deliver a persistent, team-aware retrospective with praise and growth opportunities.
Invoke the retro skill to generate the weekly retrospective for the default 7-day window.
High-intent search queries and answers about installing and using this skill.
Generate a weekly engineering retrospective by invoking the tool to analyze git commit history, work session patterns, and code-quality metrics. It compiles a structured snapshot tracking commits, insertions, deletions, and test activity for the default 7-day window.
Yes, per-author contribution breakdowns provide specific praise and growth opportunities derived from git metrics. It analyzes individual commit patterns and code quality to deliver targeted narrative summaries useful for team coaching and sprint improvements.
Team trend analysis tracks commits, lines of code inserted and deleted, test activity, code hotspots, and work session patterns. This comprehensive metric tracking ensures robust guardrails for analyzing engineering performance across a defined window.
The default analysis window is a 7-day period designed for weekly retrospectives. It supports trend analysis across a defined window, allowing you to capture engineering work patterns and code-quality metrics for broader sprint and release cycles.
Translate raw git data into actionable improvements by generating narrative summaries that identify engineering hotspots and focus patterns. These summaries convert commit history and code-quality metrics into structured coaching insights for your team.
Metrics lack per-person insights when raw git history is not compiled into a team-aware retrospective. Analyzing individual work patterns and test activity against robust guardrails structures the data into specific praise and growth opportunities.
26mitch26Analyze Git commit history to generate engineering retrospective reports.
serejarisAnalyze Claude Code history and Git data into weekly HTML reports.
shanehollomanAnalyze commit history and team activity to generate engineering retrospectives.
microwindAnalyze JavaScript code quality, performance, and security issues.
