skills.rest
AskTinNguyen
AskTinNguyenCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Summarize weekly engineering activity and code-quality signals from origin/main.

1|Updated Jan 26, 2026
Search Tags:#git#metrics#engineering#workflows#report#trend#retro
One-click install
npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill retro-asktinnguyen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/AskTinNguyen/vesper-team-skills/tree/main/gstack/retro
Command: npx skills add https://github.com/AskTinNguyen/vesper-team-skills --skill retro-asktinnguyen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospective helps teams understand how their code, workflows, and collaboration patterns impact delivery by turning raw git activity into a cohesive history and actionable insights.

Core Features & Use Cases

  • Collects commits, diffs, sessions, and branch activity from origin/main over a configurable window.
  • Computes metrics like LOC, test ratio, hotspot files, PR sizes, and streaks; generates time-series trends and a narrative summary.
  • Stores persistent retros in .context/retros for weekly comparison and long-term tracking.

Quick Start

Run the /retro command to generate this week's engineering retrospective and review the insights.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I generate an engineering retrospective report from git activity?▼

Generate an engineering retrospective by analyzing git commits, diffs, and branch activity from origin/main over a configurable time window. The process computes code-quality metrics and returns a narrative summary with actionable insights.

What engineering metrics can I track from origin/main over a 7d or 14d window?▼

Track engineering metrics like LOC, test ratio, hotspot files, PR counts, and session data over 7d, 14d, or 30d windows. Time-series trends reveal fluctuations and anomalies for comparison-based analysis.

Can I compare weekly code-quality trends and git metrics side-by-side?▼

Compare weekly code-quality trends side-by-side by applying the analysis to different time windows. Persistent retros stored in .context/retros enable long-term tracking of engineering fluctuations and anomalies.

Do I need any external dependencies to summarize commit activity and PR sizes?▼

No external dependencies are required to summarize commit activity and PR sizes. The analysis runs directly against origin/main, computing metrics like test ratio and hotspot files without additional packages.

What is the best way to identify hotspot files and anomalies in engineering workflows?▼

Identify hotspot files and anomalies by summarizing weekly engineering activity into a dense, indexable payload. The analysis computes session data and PR sizes, revealing trends and fluctuations in workflows.

Related Skills

Explore More Software Engineering Skills→
dyoshikawadyoshikawa
1

diff-analyze

Analyze git differences and commit history between the current branch and origin main.

Community
Basic
githubgithub
37.6k

powerbi-modeling

Guide Power BI semantic model design, DAX measures, and performance optimization.

Official
Advanced
AlabamaMikeAlabamaMike
3

forensic-test-analysis

Analyze git history to compute test brittleness ratios and detect large test files.

Community
Advanced
serejarisserejaris
215

cc-analytics

Analyze Claude Code history and Git data into weekly HTML reports.

Community
Intermediate