mcpField
P
printing-press-retro

printing-press-retro

github.com/mvanhornTesting & quality4.9k6.5k installsUpdated today
Repository

About printing-press-retro

printing-press-retro is a skill for maintainers or agents reviewing Printing Press runs. It guides evidence gathering and triage into a scrubbed retro and, after user approval, eligible GitHub issues for reproducible P1/P2 defects.

Key features

  1. 01Evidence gathering and session analysis
  2. 02Triage and classify defects
  3. 03Scrub retro artifacts
  4. 04Gate P1/P2 issue filing
  5. 05Requires user approval before submission

Use cases

  1. 01Reviewing a Printing Press run
  2. 02Preparing a retro for maintainers
  3. 03Deciding whether a defect merits an issue

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/mvanhorn/cli-printing-press --skill printing-press-retro

After installing, type/printing-press-retroin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

phases/
01-gather-evidence.md
02-mine-the-session.md
03-triage-candidates.md
04-classify-findings.md
05-prioritize.md
06-write-the-retro.md
07-plannable-work-units.md
08-issue-gate.md
09-package-upload-present.md
references/
artifact-packaging.md
issue-template.md
run-resolution.md
secret-scrubbing.md

Details

From the project README

/printing-press-retro

Result: A scrubbed retro document and, when the issue gate passes, GitHub issues for Printing Press defects only.

Next consumer: A maintainer or agent who will change the Printing Press (generator, scorer, skills, or binary) — not the printed CLI that just shipped.

Done: The manuscript proof exists and is scrubbed; every work unit is file-new, comment-on-existing, or local-only; no unredacted secret or PII remains; the user has the outcome list.

Intent: "Raised the floor" is analysis language, not a filing bar. File only when the Printing Press must change to stop a current, reproducible, generalizing P1 or P2 defect. Manual iteration on one CLI is expected work, not a finding. In user-facing output say "the Printing Press"; name the subsystem when pointing at a fix.

Boundaries

  • Redact every real secret and PII before quoting. Issue bodies and retro docs are public. Use references/secret-scrubbing.md Layer 0. Never quote a leaked value as evidence of the leak.
  • Don't change the machine by default. The burden of proof is on the finding.
  • No P3. File only P1/P2. Anything else is Skip or Drop, not a low-priority issue. The issue gate files P1/P2 Do work units only.
  • Never upload unscrubbed artifacts. Never modify manuscript or library source trees; scrub copies only.

Authority

Invocation authorizes reading manuscripts/library and writing the retro proof plus scratch copies. It does not authorize GitHub filing or public upload until the user confirms Submit. It does not authorize edits to the printed CLI or to Printing Press source.

Steps

Read references/run-resolution.md first. It resolves $API_NAME, $RUN_ID, $RUN_DIR, $CLI_DIR, and $IN_REPO.

Never execute a phase from memory. When you enter a phase, Read its file from phases/ first.

StepFile
1phases/01-gather-evidence.md
2phases/02-mine-the-session.md
3phases/03-triage-candidates.md
4phases/04-classify-findings.md
5phases/05-prioritize.md
6phases/06-write-the-retro.md
7phases/07-plannable-work-units.md
8phases/08-issue-gate.md
9phases/09-package-upload-present.md

Follow each file's final Next: pointer. Late procedure lives in the phase file or a role-named reference it loads (references/artifact-packaging.md, references/issue-template.md, references/secret-scrubbing.md). Do not restate those files here.

Comments

Markdown supported