skills.rest
raghavbadhwar
raghavbadhwarCOMMUNITY
Explore all skills by this author →
GitHub

gstack-openclaw-retro

Generates weekly engineering retrospectives from git commit history with team metrics and trend tracking.

Updated Aug 9, 2026
Search Tags:#code quality#git#retrospective#engineering metrics#commit analysis#trend tracking#team analytics
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill gstack-openclaw-retro-raghavbadhwar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gstack-openclaw-retro
Source: https://github.com/raghavbadhwar/rstack/tree/main/openclaw/skills/gstack-openclaw-retro
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill gstack-openclaw-retro-raghavbadhwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams lack a structured, data-driven way to review what shipped each week, how work patterns evolve, and where code quality is trending, forcing managers to manually dig through git logs. ## Core Features & Use Cases - Commit and Metrics Analysis: Aggregates commits, PRs, LOC, test ratios, hotspots, and session patterns from git history over configurable windows (24h, 7d, 14d, 30d). - Team-Aware Breakdowns: Produces per-contributor leaderboards with praise and growth areas anchored in actual commits, plus streak tracking and focus scores. - Persistent Trend Tracking: Saves JSON snapshots to memory/ and compares against prior retros to show week-over-week deltas. - Use Case: A tech lead asks for the weekly retro before a Monday standup and receives a Telegram-formatted summary covering shipping velocity, code quality signals, and three actionable improvements. ## Quick Start Ask the agent to run the weekly engineering retro for the last 7 days of this repository.

Frequently Asked Questions about gstack-openclaw-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 in a git repository and it runs git log queries against origin/main for the last 7 days by default. It computes commits, LOC, test ratios, sessions, and per-author breakdowns, then formats a narrative summary.

How to compare this week's engineering metrics against last week?▼

Use the compare argument to run the retro for the current window and the prior same-length window side by side. It shows metric deltas with arrows indicating improvement or regression, and also loads prior snapshots from the memory directory.

What time windows does the engineering retro support?▼

The default window is 7 days, with options for 24h, 14d, and 30d. Day-based windows align to local midnight, and all times are reported in the user's local timezone.

Does the retro work for solo repositories without a team?▼

Yes, it detects the current user via git config and skips the team breakdown when only one contributor exists. The personal deep-dive with session analysis, focus score, and streak tracking still applies.

Why does the retro report BLOCKED status?▼

The retro reports BLOCKED when the working directory is not a git repository or when no commits exist in the requested window. Ensure you are inside a repo with commits on origin/main for the selected period.

Related Skills

Explore More Software Engineering Skills→
udecodeudecode
1.2k

creating-pr

Create or update GitHub pull requests with conventional commits.

Official
Intermediate
ComputerConnectionComputerConnection

sprint-retro

Collect sprint phase data and generate a Sprint Retro document.

Community
Advanced
MonumentalSystemsMonumentalSystems
17

quality-metrics

Define QA standards for test coverage, code quality, and defect metrics.

Official
Advanced
zz8011zz8011

retro

Analyze commit history and code-quality metrics to summarize weekly engineering retrospectives.

Community
Advanced