skills.rest
diiviikk5
diiviikk5COMMUNITY
Explore all skills by this author →
Website𝕏@divikkk1GitHub

rezops-openclaw-retro

Aggregates weekly commit history and team activity into retrospective reports with per-person praise and growth trends.

Updated Apr 22, 2026
Search Tags:#automation#git#metrics#engineering#leadership#team#retro
One-click install
npx skills add https://github.com/diiviikk5/rezops --skill rezops-openclaw-retro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rezops-openclaw-retro
Source: https://github.com/diiviikk5/rezops/tree/main/openclaw/skills/rezops-openclaw-retro
Command: npx skills add https://github.com/diiviikk5/rezops --skill rezops-openclaw-retro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospective automation analyzes commit history, work patterns, and code quality metrics to provide persistent history and growth-oriented feedback for teams.

Core Features & Use Cases

  • Team-aware retros with per-person contributions, praise, and growth opportunities.
  • Analyzes commit history, contributor activity, and quality metrics with persistent history and trend tracking.
  • Generates per-author leaderboards and narratives suitable for team updates and post-mortems.

Quick Start

Run the retro for the default 7-day window to generate team metrics and growth insights.

Frequently Asked Questions about rezops-openclaw-retro

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

FAQPage Schema
How do I generate automated weekly engineering retrospectives from git commit history?▼

Weekly engineering retrospectives analyze git commit history and per-author statistics to generate team-aware narratives, highlighting individual contributions, praise, and growth opportunities.

What metrics are included in a team-focused engineering retro?▼

Team-focused engineering retros include per-author statistics, contributor activity, code quality metrics, and trend analyses to deliver per-person praise and growth areas.

Can I use engineering retro insights for Telegram-style team updates?▼

Engineering retro insights generate team-aware narratives and per-author leaderboards suitable for formatting into Telegram-style reports and team post-mortems.

Does the weekly retro analysis support persistent history tracking for software teams?▼

Weekly retro analysis supports persistent history tracking, allowing software engineering teams to monitor contributor activity and growth trends over multiple retrospective cycles.

What do I need to run an automated engineering retro for my team?▼

To run an automated engineering retro, you need access to your team's git commit history for the default 7-day window to aggregate work patterns and generate growth-oriented feedback.

How do engineering leadership teams use automated retro insights for post-mortems?▼

Engineering leadership teams use automated retro insights to analyze contributor activity and quality metrics, generating per-author leaderboards and narratives suitable for team post-mortems and updates.

Related Skills

Explore More Software Engineering Skills→
ecosyste-msecosyste-ms
1

commits

Analyze commit history and contributor statistics for public repositories.

Official
Intermediate
serejarisserejaris
215

cc-analytics

Analyze Claude Code history and Git data into weekly HTML reports.

Community
Intermediate
nuurpronuurpro
1

retro

Analyze local git history to summarize weekly engineering activity and suggest next-sprint focus areas.

Community
Advanced
imonmiimonmi

retro

Analyze weekly commit history and code quality for team retrospectives.

Community
Advanced