workflow-retro

Analyze review feedback patterns and propose improvements to skills and project config files.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/mcmurrym/coding-agent-skills --skill workflow-retro-mcmurrym
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-retro
Source: https://github.com/mcmurrym/coding-agent-skills/tree/main/agent-skills/workflow-retro
Command: npx skills add https://github.com/mcmurrym/coding-agent-skills --skill workflow-retro-mcmurrym

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) components.

What problem does it solve? Review cycles often surface the same preventable issues repeatedly—missing tests, lint failures, incomplete PRs—costing extra fix-up commits and review rounds. This Skill turns each session's review feedback into concrete, approved improvements to your CLAUDE.md, AGENTS.md, cursor rules, and skill files, and tracks recurring findings across sessions so fixes that didn't hold get strengthened. ## Core Features & Use Cases - Evidence gathering: Scans conversation context, git log fix-up commits, and PR review threads to build a deduplicated list of findings. - Root-cause classification: Labels each finding as preventable by instruction, by an existing skill, by a new skill, or not preventable. - Recurrence tracking: Maintains a persistent JSON retro log (stored in the git directory) with keyword-based search to surface repeat issues across sessions. - Human-in-the-loop proposals: Presents one diff proposal at a time targeting canonical files (resolving symlinks), applying changes only after explicit approval. - Use Case: After a PR required three review rounds for missing tests and lint errors, run a retro to add a test-coverage rule to CLAUDE.md and a verification step to your make-pr skill, then log both findings for future recurrence checks. ## Quick Start Use the workflow-retro skill to analyze this session's review feedback and propose improvements to my project config files.

Frequently Asked Questions about workflow-retro

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

FAQPage Schema
How do I analyze review feedback patterns from a coding session?▼

Run the workflow-retro skill after a review cycle. It scans conversation context, git log fix-up commits, and PR review threads to build a deduplicated findings list, then classifies each finding by whether a config rule or skill step could have prevented it.

How to track recurring code review issues across sessions?▼

The skill appends every finding to a persistent retro-log.json file stored in the git directory via the retro-log.sh script. Its search command matches new findings against past entries by keyword overlap, flagging repeats and fixes that didn't hold.

Does workflow-retro modify files automatically?▼

No. Every improvement is presented as a single diff proposal requiring explicit user approval (discuss, apply, or skip) before any edit is made. It also never modifies application code—only workflow and config artifacts like CLAUDE.md or skill files.

Can workflow-retro handle symlinked config files like CLAUDE.md?▼

Yes. The skill resolves symlinks before reading or editing, deduplicates files pointing to the same target, and always applies changes to the canonical real file while noting which files are symlinked to it.

What are the limitations of workflow-retro?▼

It does not create new skills (only flags when one might be needed), does not modify application code, and does not run automatically—it must be manually invoked. Findings classified as not preventable are logged but receive no proposal.