skills.rest
louisfghbvc
louisfghbvcCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze commit history and code quality metrics to summarize engineering activity.

4|1|Updated Sep 13, 2023
Search Tags:#git#retrospective#engineering#commit-history#retro#praise#team-growth
One-click install
npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill retro-louisfghbvc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/louisfghbvc/mcp-leetcode-crawler/tree/main/.agent/skills/retro
Command: npx skills add https://github.com/louisfghbvc/mcp-leetcode-crawler --skill retro-louisfghbvc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives are hard to coordinate and synthesize from raw commits and tickets. This skill analyzes commit history, work patterns, and code quality metrics to surface team contributions, patterns, and growth areas.

Core Features & Use Cases

  • Team-aware contributions: breaks down per-person contributions with praise and growth areas.
  • Persistent history and trend tracking across sprints.
  • Proactive suggestions at the end of a work week or sprint.

Quick Start

Ask your assistant to run a weekly retro to generate team insights from the latest commits and PRs.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate a weekly retrospective from git commit history?▼

Running a weekly retro analyzes git commit history, work patterns, and code quality metrics to summarize engineering activity. It outputs a concise narrative with team trends, per-person praise, and actionable growth recommendations.

What is the best way to summarize engineering activity for sprint reviews?▼

Summarizing engineering activity for sprint reviews involves analyzing commit history and code quality metrics to surface per-person contributions. This produces a concise narrative highlighting team trends and growth opportunities for retrospective meetings.

Can I track team growth and persistent trends across sprints using commit history?▼

Yes, you can track team growth across sprints by analyzing commit history and work patterns. This process maintains persistent history and trend tracking, surfacing per-person praise and actionable growth opportunities for engineering teams.

Does this retrospective tool support per-person praise and contribution breakdowns?▼

Yes, the retrospective tool breaks down per-person contributions from commit history and work patterns. It applies team-aware analysis to surface individual praise and growth areas within the weekly retrospective narrative.

How do I generate actionable recommendations for engineering team health checks?▼

Generating actionable recommendations for team health checks requires analyzing commit history and code quality metrics. This surfaces work patterns and growth opportunities, outputting a concise narrative with trends to improve engineering team health.

What do I need to run a team retrospective from our repository's PRs and commits?▼

To run a team retrospective from PRs and commits, you need access to your repository's commit history and work pattern data. The analysis generates team insights, contribution breakdowns, and growth recommendations without additional dependencies.

Related Skills

Explore More Software Engineering Skills→
garrytangarrytan
127.1k

gstack-openclaw-retro

Generate engineering retrospective reports from git commit history and code quality metrics.

Community
Advanced
JeremiahEllingtonJeremiahEllington

retro

Analyze git commit history and work patterns to generate team-wide retrospectives with per-person insights.

Community
Advanced
Fantasia1999Fantasia1999

scrum-master

Analyze sprint data with Python scripts for forecasting and health scoring.

Community
Advanced
yocxy2yocxy2

retro

Analyze commit history and work patterns to generate engineering retrospective reports.

Community
Advanced