Install any skill in seconds. Free to start, no credit card required.
Get Started Free →garrytan/gstack-openclaw-retro
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware with per-person contributions, praise, and growth areas.
Passed 15 of 19 test cases with the skill, and 8 of 19 without it.
and 8 more in the full report
9 fixed8 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the hotspot analysis section listing top modified files, what specific commit frequency threshold qualifies a file to be flagged as a churn hotspot?
| Checked | Without skill | With skill |
|---|---|---|
| Files changed 5 or more times are flagged as churn hotspots. | Missed | Passed |
The instructions your model reads when the skill loads.
Generates a comprehensive engineering retrospective analyzing commit history, work patterns, and code quality metrics. Team-aware: identifies the user running the command, then analyzes every contributor with per-person praise and growth opportunities.
24h: last 24 hours14d: last 14 days30d: last 30 dayscompare: compare current window vs prior same-length windowParse the argument to determine the time window. Default to 7 days. All times should be reported in the user's local timezone.
Midnight-aligned windows: For day units, compute an absolute start date at local midnight. For example, if today is 2026-03-18 and the window is 7 days, the start date is 2026-03-11. Use --since="2026-03-11T00:00:00" for git log queries. For hour units, use --since="N hours ago".
First, fetch origin and identify the current user:
git fetch origin main --quiet
git config user.name
git config user.email
The name returned by git config user.name is "you" ... the person reading this retro. All other authors are teammates.
Run ALL of these git commands (they are independent):
# All commits with timestamps, subject, hash, author, files changed
git log origin/main --since="<window>" --format="%H|%aN|%ae|%ai|%s" --shortstat
# Per-commit test vs total LOC breakdown with author
git log origin/main --since="<window>" --format="COMMIT:%H|%aN" --numstat
test cases passed, vs 8 / 19 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.