Printing Press Retro
mvanhorn/cli-printing-pressAfter you generate a CLI with the Printing Press, you can run a retrospective to find ways to make the whole system better. This is not about fixing the CLI you just made. It is about improving the templates, the Go binary, the skills, and the catalog so the next CLI comes out stronger.
The retro looks at what went wrong and asks if the machine could have prevented it or given you a better starting point. If the issue would happen again on other CLIs, it becomes a finding. The skill then creates a GitHub issue with those findings so the Printing Press can be improved.
Add Printing Press Retro skill to your workflow
Global
mkdir -p ~/.claude/skills/printing-press-retroProject
mkdir -p .claude/skills/printing-press-retroSource Repository
More Code Review & Quality Claude Code Skills
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective