retro

Analyze weekly commit history and code changes to generate plan-ready summaries.

Updated Dec 13, 2017
One-click install
npx skills add https://github.com/dogeared/tnra --skill retro-dogeared
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/dogeared/tnra/tree/main/.claude/skills/gstack/retro
Command: npx skills add https://github.com/dogeared/tnra --skill retro-dogeared

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to turn weekly engineering activity into concrete improvements. It surfaces per-person contributions, hotspots in code, and growth opportunities so leaders can act.

Core Features & Use Cases

  • Identify top contributors and growth areas with per-person praise and guidance.
  • Highlight hotspots in files, PR sizes, and focus scores to drive process improvements.
  • Produce a plan-ready summary for stakeholders and cross-project comparisons.

Quick Start

Run the retro command to generate the weekly retrospective for the default 7-day window.

Frequently Asked Questions about retro

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a weekly engineering retrospective from git history?

Generate a weekly engineering retrospective by running the retro command to analyze the default 7-day window of commit history. It computes code changes and contributor behavior to surface actionable insights for your team.

What metrics should an engineering team retrospective include?

An engineering team retrospective should include per-person praise and growth opportunities, file hotspots, focus scores, and PR size distributions to highlight process improvement areas.

Can I analyze contributor behavior and PR sizes for process improvement?

Yes, you can analyze contributor behavior and PR size distributions for process improvement. The retrospective evaluates commit history to identify growth areas and workflow bottlenecks.

How do I identify code hotspots and focus scores from recent commits?

Identify code hotspots and focus scores from recent commits by analyzing your weekly git activity. The retrospective surfaces file hotspots and calculates focus scores based on contributor behavior.

Does the retro analysis require any external dependencies or setup?

The retro analysis requires no external dependencies. It handles end-to-end data gathering, metric computation, and user-facing reporting with validation and privacy considerations directly from your commit history.

Can I share the engineering retrospective summary with stakeholders?

Yes, you can share the engineering retrospective summary with stakeholders. It produces a plan-ready summary of weekly activity that can be shared directly or copied into planning documents.