skills.rest
0xHarbs
0xHarbsCOMMUNITY
Explore all skills by this author →
𝕏@0xHarbsGitHub

retro

Aggregate commit history and code quality metrics into a weekly retrospective JSON.

1|Updated Mar 20, 2026
Search Tags:#automation#git#workflow#metrics#engineering#retro
One-click install
npx skills add https://github.com/0xHarbs/agent-setup --skill retro-0xharbs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/0xHarbs/agent-setup/tree/main/claude/skills/lifecycle/retro
Command: npx skills add https://github.com/0xHarbs/agent-setup --skill retro-0xharbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly retrospectives synthesize codebase dynamics into actionable guidance for engineering teams, helping leaders and ICs align on improvements and predict next-week focus.

Core Features & Use Cases

  • Automated collection of commit history, work patterns, and code quality metrics to generate a structured retro.
  • Produces retro-actions.json consumed by /review and /plan skills to drive follow-up.
  • Generates a narrative summary and a .context/retros history for long-term trends.

Quick Start

Invoke the retro skill to generate this week's retrospective.

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 using git history and code quality metrics?▼

Yes, you can compare engineering work patterns week-over-week. The retrospective covers a 7-day window with an optional comparison to the prior week, generating a local .context/retro-result.json and a .context/retros history to track long-term trends.

What engineering metrics are needed to generate an actionable codebase retrospective?▼

Generating an actionable codebase retrospective requires aggregating commit history, code quality metrics, and collaboration signals. The skill synthesizes these codebase dynamics into structured guidance, helping engineering leaders and individual contributors align on improvements and predict next-week focus.

Can I use automated retrospective outputs to drive sprint planning and code review workflows?▼

Automated weekly retrospectives are designed for mid to senior-level software projects. They synthesize codebase dynamics into actionable guidance, making them best suited for teams needing structured alignment on engineering improvements rather than individual contributors working in isolation.

How does tracking retrospective history help predict next-week engineering focus?▼

Tracking retrospective history helps predict next-week engineering focus by maintaining a local .context/retros history for long-term trends. By analyzing aggregated commit history and code quality metrics over consecutive 7-day windows, teams can identify recurring patterns and proactively address workflow bottlenecks.

Related Skills

Explore More Software Engineering Skills→
studyzystudyzy

retro

Analyze git history and code metrics to generate weekly engineering retrospectives.

Community
Advanced
robotics-playgroundrobotics-playground

bmad-retrospective

Extract patterns from past sprints and generate action items for epic retrospectives.

Official
Advanced
ThiagoVitaleThiagoVitale

gsd-workstreams

Manage and automate parallel workstream operations with Codex collaboration tools.

Community
Advanced
algorithmbasicsalgorithmbasics

gstack-openclaw-retro

Analyze git history to generate weekly engineering retrospectives with per-author insights.

Community
Advanced