skills.rest
vnmoorthy
vnmoorthyCOMMUNITY
Explore all skills by this author →
GitHub

gstack-openclaw-retro

Analyze commits, PRs, LOC, and team patterns to generate weekly engineering retrospectives.

2|1|Updated Mar 5, 2026
Search Tags:#automation#git#metrics#retrospective#reporting#engineering#team-analysis
One-click install
npx skills add https://github.com/vnmoorthy/Skylog --skill gstack-openclaw-retro-vnmoorthy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/vnmoorthy/Skylog/tree/main/.claude/skills/gstack/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/vnmoorthy/Skylog --skill gstack-openclaw-retro-vnmoorthy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly engineering retrospectives help teams reflect on their codebase activity, identify patterns, and plan improvements without manual data wrangling.

Core Features & Use Cases

  • Automated retrospective generation: analyzes commit history, PRs, test activity, and code quality metrics to produce a cohesive narrative.
  • Team-aware insights: recognizes per-person contributions, praise, and growth opportunities with persistent history.
  • Use Case: run a weekly retro to review shipped features, quality trends, and collaboration patterns.

Quick Start

Run the retro tool against the target repository to generate the current week's storytelling report.

Frequently Asked Questions about gstack-openclaw-retro

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

FAQPage Schema
How do I automate weekly engineering retrospectives from git history?▼

Automate weekly engineering retrospectives by analyzing a repository's commits, PRs, and LOC to generate an actionable narrative. The tool automatically extracts metrics, identifies hotspots, and provides a Telegram-ready storytelling report covering trends and growth opportunities.

What engineering metrics are included in an automated retrospective report?▼

Automated retrospective reports include commit history, pull request activity, lines of code, hotspots, and team patterns. The metrics feature per-author breakdowns and focus scores, providing a comprehensive view of engineering activity over a configurable time window.

Can I generate per-author breakdowns and team patterns for a specific time window?▼

Yes, you can generate per-author breakdowns and team patterns over a configurable time window. The analysis recognizes individual contributions, praise, and growth opportunities while maintaining persistent history to track team collaboration patterns over time.

Does the retrospective tool require any external dependencies to analyze PRs and commits?▼

No external dependencies are required to analyze PRs and commits. The tool operates independently to process git repository activity, extracting commit history and pull request data to produce a cohesive weekly retrospective narrative.

What's the best way to share engineering metrics and retrospective insights with my team?▼

Share engineering metrics and retrospective insights using the tool's built-in Telegram-ready narrative output. The generated report provides a storytelling format that covers shipped features, quality trends, and collaboration patterns suitable for direct team distribution.

Related Skills

Explore More Software Engineering Skills→
opendatahub-ioopendatahub-io
36

shallow-clone

Creates a depth-1 clone of a Git repository in a temporary location.

Official
Intermediate
binfen1binfen1

gstack-openclaw-retro

Analyzes commit history to generate weekly engineering retrospectives with per-person metrics and Telegram-ready narratives.

Community
Advanced
GrassHopper42GrassHopper42

gstack-openclaw-retro

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

Community
Advanced
fghaffarfghaffar

retro

Generate weekly engineering retrospective reports from Git commit history and metrics.

Community
Advanced