What problem does it solve? Single lessons get captured in the moment, but patterns like recurring-fix files, fix-heavy commit mixes, and shrinking test-to-code ratios only become visible when you deliberately review a whole window of work. This Skill performs that periodic retrospective over git history, merged PRs, and skill-usage logs, turning raw history into concrete improvement decisions. ## Core Features & Use Cases - Signal computation: Parses conventional-commit types, file hotspots, recurring-fix files, test-to-production ratio, PR size distribution, and regressions from git log and GitHub PRs. - Decision-oriented report: Produces a window summary where every signal that warrants action maps to a concrete change such as a test to add, a file to refactor, or a convention to adopt. - Pattern routing: Routes durable, generalizable patterns to the companion lesson-capture skill for human-confirmed recording, while writing nothing itself. - Use Case: At the end of a sprint, ask for a retro since the last release and receive a report showing that one adapter file received three fix commits, the test ratio dropped, and PRs grew large, each paired with a specific remediation. ## Quick Start Ask the agent to run a retrospective over the last two weeks of git history and merged PRs and report the signals with improvement decisions.