skills.rest
miko06
miko06COMMUNITY
Explore all skills by this author →
GitHub

retro

Analyze team contributions and code quality metrics to generate weekly engineering retrospective reports.

Updated Jun 16, 2026
Search Tags:#code quality#retrospective#commit history#team analysis#engagement report
One-click install
npx skills add https://github.com/miko06/MedicineSimulator --skill retro-miko06
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/miko06/MedicineSimulator/tree/main/.opencode/skills/gstack-retro
Command: npx skills add https://github.com/miko06/MedicineSimulator --skill retro-miko06

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, read, write, glob, askuserquestion, filesystem, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of conducting weekly engineering retrospectives, making it easier to review work patterns, commit history, and code quality metrics.

Core Features & Use Cases

  • Review Work Patterns: Analyze team contributions, work patterns, and code quality metrics with persistent history and trend tracking.
  • Track Commit History: Break down per-person contributions with praise and growth areas, using commit history analysis.
  • Use Case: Use this Skill to automatically generate a comprehensive weekly engineering report that can be reviewed with the team.

Quick Start

Invoke the 'retro' skill to generate a report for the current sprint.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate weekly engineering retrospectives and analyze team contributions?▼

Automate weekly engineering retrospectives by analyzing team contributions, work patterns, and commit history to generate comprehensive reports. This process breaks down per-person contributions into praise and growth areas while tracking quality metrics.

What is the best way to track code quality metrics and commit history for a sprint review?▼

Track code quality metrics and commit history by analyzing per-person contributions with persistent history and trend tracking. This approach breaks down individual work patterns into praise and growth areas for comprehensive sprint reviews.

Do I need bash and filesystem access to generate a team engagement report?▼

Yes, generating a team engagement report requires bash, read, write, glob, askuserquestion, and filesystem access. These dependencies are necessary to analyze commit history and code quality metrics and generate comprehensive retrospective reports.

Can I use this approach to review work patterns for individual team members?▼

Yes, you can review work patterns for individual team members by breaking down per-person contributions. The analysis highlights praise and growth areas using commit history, providing targeted feedback for each developer.

What limits or prerequisites should I consider when setting up code quality retrospective analysis?▼

Code quality retrospective analysis requires an environment with bash, read, write, glob, askuserquestion, and filesystem access. It is designed for weekly sprint cycles and relies on accessible commit history to generate accurate engagement reports.

Related Skills

Explore More Software Engineering Skills→
ericdahl-devericdahl-dev

retro

Analyze commit history, work patterns, and code quality metrics for weekly engineering retrospectives.

Official
Intermediate
shekerkammashekerkamma

retro

Analyze git commit history and code quality metrics to generate weekly engineering retrospective reports.

Community
Advanced
JeremiahEllingtonJeremiahEllington

retro

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

Community
Advanced
diptanshuagrawaldiptanshuagrawal

doc-sync-digest

Post a document review digest to a Slack team channel.

Community
Intermediate