printing-press-retro

Runs retrospectives on Printing Press CLI generation runs and files triaged GitHub issues.

1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/filippolmt/skills --skill printing-press-retro-filippolmt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: printing-press-retro
Source: https://github.com/filippolmt/skills/tree/main/skills/printing-press-retro
Command: npx skills add https://github.com/filippolmt/skills --skill printing-press-retro-filippolmt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? After a Printing Press run generates a CLI, friction, defects, and scorer problems are easy to forget or misfile. This Skill mines the session and run artifacts, triages findings against a strict evidence bar, and files only reproducible P1/P2 defects as labeled GitHub issues. ## Core Features & Use Cases - Nine-phase retro pipeline: Gathers run evidence, mines the session transcript for seven signal categories, triages candidates, classifies findings by component, and prioritizes into Do/Skip/Drop buckets. - Secret and PII scrubbing: Redacts credentials and personal data from retro documents and issue bodies before any public upload, with hard-fail behavior on unredacted vendor tokens. - GitHub issue filing with dedup: Groups findings into work units, deduplicates against open retro issues, files new issues or comments on existing ones with source:retro, comp:<slug>, and priority:P1/P2 labels. - Use Case: After generating a CLI for a new API, run the retro to surface a recurring template gap, scrub the evidence, and file a labeled enhancement issue on the Printing Press repo with uploaded manuscript artifacts. ## Quick Start Ask the assistant to run a retrospective on the latest Printing Press run for a given API and file the resulting findings.

Frequently Asked Questions about printing-press-retro

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

FAQPage Schema
How do I run a retrospective on a Printing Press CLI generation run?

Invoke the retro skill after a printed-CLI run; it resolves the API and run from the manuscripts directory, gathers evidence, mines the session, and writes a scrubbed retro document. Findings that pass the issue gate are filed as GitHub issues after you confirm submission.

What kinds of findings get filed as GitHub issues?

Only P1 defects (broken or unsafe printed CLI) and P2 defects (generalizing issues where the CLI still works) are filed. Each work unit gets exactly one bug or enhancement type label plus comp:<slug> and priority labels; P3-level items are skipped or dropped.

Does the retro skill upload artifacts publicly?

Uploads to catbox.moe happen only after explicit user confirmation and a successful secret-scrub verification. If either gate fails, the skill refuses the upload and keeps local copies in the manuscript proofs and a temp scratch directory.

How does the skill avoid filing duplicate GitHub issues?

Before filing, it lists open issues labeled source:retro or legacy retro and classifies each work unit as same, related-area, or unrelated. Matches become comments on the existing issue; uncertain cases bias toward filing new.

When should I not use the printing-press retro skill?

Do not use it for polishing a single printed CLI or fixing one CLI's quirk; those are per-CLI fixes, not retro findings. It also does not apply before any Printing Press run exists, since it requires manuscript artifacts to analyze.