skills.rest
kirvin
kirvinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

retro

Analyze git log and beads closed-issue data to generate improvement issues.

Updated Apr 3, 2026
Search Tags:#retrospective#pattern analysis#git log#work analysis#improvement issues
One-click install
npx skills add https://github.com/kirvin/agent-dev-harness --skill retro-kirvin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: retro
Source: https://github.com/kirvin/agent-dev-harness/tree/main/plugins/kf/skills/retro
Command: npx skills add https://github.com/kirvin/agent-dev-harness --skill retro-kirvin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ce:post-mortem, beads, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of conducting a comprehensive retrospective over a span of work, analyzing git log and beads closed-issue data, and generating actionable improvement issues.

Core Features & Use Cases

  • Data Gathering: Collects git log and beads closed-issue data.
  • Pattern Analysis: Delegates pattern analysis to ce:post-mortem.
  • Issue Creation: Converts findings into actionable beads improvement issues.
  • Use Case: Ideal for reviewing multiple tasks and identifying systemic issues.

Quick Start

Run the retro skill to generate a comprehensive retrospective report for the last two weeks of work.

Frequently Asked Questions about retro

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

FAQPage Schema
How do I automate a retrospective analysis using git log data?▼

Automating a retrospective with git log data involves collecting commit history and closed-issue records to identify systemic patterns. This skill analyzes spans of work to generate actionable improvement issues automatically.

What is the best way to identify systemic improvement issues from closed tickets?▼

Identifying systemic issues from closed tickets requires pattern analysis across work spans. By analyzing closed-issue data and git history, this skill highlights recurring problems and converts findings into actionable improvement tickets.

How do I run a comprehensive retrospective for a two-week work span?▼

Running a retrospective for a two-week span requires gathering git log and closed-issue data from that period. The skill processes this timeframe to generate a comprehensive report identifying work patterns and improvement areas.

Do I need post-mortem analysis tools to generate retrospective reports?▼

Generating retrospective reports requires a post-mortem tool for pattern analysis. This skill delegates pattern identification to ce:post-mortem and uses beads to create actionable improvement issues from the findings.

Can I convert retrospective findings directly into actionable tickets?▼

Converting retrospective findings into actionable tickets is supported by integrating with beads for issue creation. The skill takes identified patterns from git log and closed-issue analysis and outputs structured improvement issues.

What are the limitations of using git log for work pattern analysis?▼

Using git log for work pattern analysis limits retrospectives to development activity captured in commits. It requires corresponding closed-issue data from beads to provide a comprehensive view of systemic problems across multiple tasks.

Related Skills

Explore More Software Engineering Skills→
AGMO-IncAGMO-Inc
4

retro

Analyze Git history to generate weekly retrospective reports.

Official
Advanced
bmad-code-orgbmad-code-org
8

bmad-os-root-cause-analysis

Correlate git history and PR metadata to generate root cause analysis reports.

Official
Advanced
oldwinteroldwinter
5

skill-review

Analyze conversation logs to identify and prioritize AI skill issues.

Community
Intermediate
dallenpyrahdallenpyrah

learn

Automate post-mortem documentation from GitHub issues, pull requests, and git logs.

Community
Advanced