retro

Analyzes commit history and work patterns to generate weekly engineering retrospectives with trend tracking.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a weekly engineering retrospective means digging through git logs, remembering what shipped, and tracking team contributions by hand. This Skill automates that analysis and keeps a persistent history so trends are visible across weeks. ## Core Features & Use Cases - Commit and Work Pattern Analysis: Reviews commit history and code quality metrics to summarize what the team shipped during the week or sprint. - Team-Aware Breakdowns: Breaks down per-person contributions with praise and growth areas for each team member. - Persistent History and Trends: Stores prior retros, timeline events, and learnings per project so each new retrospective can compare against past weeks. - Use Case: At the end of a sprint, ask for a weekly retro and receive a structured report covering shipped work, individual contributions, and trends versus previous retros. ## Quick Start Ask the assistant to run a weekly retro for this repository to analyze the recent commit history and produce a team retrospective report.

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?

Invoke the retro skill with a phrase like "weekly retro" or "what did we ship". It analyzes commit history and work patterns, then produces a structured retrospective with per-person contributions and trend comparisons against prior weeks.

What does the retro skill analyze in a repository?

It analyzes commit history, work patterns, and code quality metrics for the current project. It also loads prior retros, recent timeline events, and recorded learnings from the project's persistent gstack storage to provide trend context.

Does the retro skill track trends across multiple weeks?

Yes. It stores each retrospective in a per-project directory and loads up to five prior retros when generating a new one. This lets it highlight trends in output, quality, and team contributions over time.

Can the retro skill break down contributions per team member?

Yes. The skill is team-aware and breaks down per-person contributions, including praise and growth areas for each contributor, based on the commit history and work patterns it analyzes.

When should I run an engineering retrospective with this skill?

Run it at the end of a work week or sprint. The skill is designed to be proactively suggested at those boundaries, and it works best when run regularly so its persistent history can surface meaningful trends.