skills.rest
AkbarDevop
AkbarDevopCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze commit history, PRs, and test signals to generate engineering retrospective snapshots.

Updated Mar 12, 2026
Search Tags:#engineering#code-quality#velocity#commit-history#session-analysis#retro
One-click install
npx skills add https://github.com/AkbarDevop/gstack-codex --skill retro-akbardevop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/AkbarDevop/gstack-codex/tree/main/retro
Command: npx skills add https://github.com/AkbarDevop/gstack-codex --skill retro-akbardevop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives help teams understand shipping velocity, work patterns, and code quality trends over time, enabling data-driven improvements.

Core Features & Use Cases

  • Automated collection of commit histories, PR activity, and test signals to reveal velocity, hotspots, and quality metrics.
  • Trend-aware narrative generation that highlights focus areas, risks, and actionable next steps for engineering teams.
  • Customizable windows (7d, 14d, 30d) and compare mode to surface week-over-week changes.

Quick Start

Run retro to generate the latest seven-day engineering retrospective.

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 from git commit history and PR activity?▼

To generate an engineering retrospective, this Skill parses git commit histories, diff statistics, PR references, and test signals to output a structured snapshot of velocity, quality trends, and collaboration patterns.

What is the best way to track software team velocity and code quality trends over time?▼

Tracking software team velocity and code quality trends is achieved by analyzing engineering activity within customizable windows like 7, 14, or 30 days, surfacing week-over-week changes for data-driven process improvements.

Can I use commit history analysis for custom time windows beyond a standard weekly retrospective?▼

Yes, commit history analysis supports custom windows including 7-day, 14-day, and 30-day periods, alongside a compare mode to expose week-over-week changes in shipping velocity and work patterns.

How does session analysis expose engineering collaboration patterns and risks?▼

Session analysis exposes engineering collaboration patterns and risks by parsing git history and diff statistics to reveal activity hotspots, focus areas, and actionable next steps for the team.

Do I need specific test signal integrations to analyze code quality trends in a weekly retro?▼

Yes, parsing test indicators and signals is required alongside commit histories and PR activity to accurately expose code quality trends and guide engineering accountability within the retro snapshot.

Related Skills

Explore More Software Engineering Skills→
fghaffarfghaffar

retro

Generate weekly engineering retrospective reports from Git commit history and metrics.

Community
Advanced
anishs1207anishs1207
1

retro

Analyze weekly git history to generate retrospective insights and trend analyses.

Community
Advanced
alexmaruccialexmarucci

cicd

Monitor CI/CD pipeline metrics, tests, and deployment gates via Datadog.

Community
Advanced
zhifengzhang-szzhifengzhang-sz

retro

Analyzes tracked time and generates weekly reports for managers and teams, highlighting progress and areas for attention.

Community
Advanced