gstack-retro

Generate weekly engineering retrospectives from commit history and quality metrics.

Updated May 19, 2026
One-click install
npx skills add https://github.com/anilveersingh1308/copilot-skills --skill gstack-retro-anilveersingh1308
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gstack-retro
Source: https://github.com/anilveersingh1308/copilot-skills/tree/main/.github/skills/gstack-retro
Command: npx skills add https://github.com/anilveersingh1308/copilot-skills --skill gstack-retro-anilveersingh1308

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered commit activity into a clear weekly engineering retrospective, including per-person contribution breakdowns and trend-aware quality metrics, so teams stop guessing and start improving with consistent signals.

Core Features & Use Cases

  • Weekly retro from shipping evidence: Synthesizes commit history and work patterns into a structured retrospective narrative aligned to team outcomes, not just a changelog; use it at the end of each week or sprint when asked for “weekly retro” or “what did we ship”.
  • Persistent history and trend tracking: Loads prior retros and a recent timeline/learnings context from gstack project artifacts to summarize what improved, what regressed, and what to focus on next.
  • Team-aware feedback with actionable growth areas: Breaks down per-person contributions, provides praise, and identifies growth opportunities while keeping the output focused on engineering quality and delivery.

Quick Start

Ask for the weekly retrospective by saying: weekly retro for this project.

Frequently Asked Questions about gstack-retro

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

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

You can generate a per-person engineering retrospective by prompting for a weekly retro. The Skill analyzes commit history and work patterns to produce a team-aware breakdown of individual contributions, praise, and growth opportunities.

How does trend tracking work for team code quality metrics?

Trend tracking for code quality metrics works by loading prior retros and learnings from persistent filesystem context. This allows the Skill to compare current commit history against past performance and summarize what improved, what regressed, and what to focus on next.

Can I use this for end-of-sprint reporting on individual developer contributions?

Yes, you can use this for end-of-sprint reporting on developer contributions. The Skill responds to end-of-sprint prompts by providing a team-aware, per-person breakdown of individual contributions, praise, and actionable growth areas.

Do I need filesystem context to track engineering retrospective trends?

Yes, filesystem-based context queries are required to track engineering retrospective trends. The Skill queries persistent project artifacts for prior retros, timelines, and learnings to maintain trend awareness across your weekly reports.

What is the best way to summarize what we shipped this week from git activity?

The best way to summarize what you shipped from git activity is to prompt the Skill with a query like what did we ship. It analyzes commit history and work patterns to produce a structured retrospective narrative focused on engineering quality and delivery outcomes.