mvanhorn/printing-press-output-review

Sous-compétence interne : examen agentique de la sortie échantillonnée d'une CLI imprimée pour détecter des problèmes de plausibilité que les vérifications basées sur des règles ne peuvent pas encoder (pertinence de correspondance de sous-chaîne, bugs de format, suppressions silencieuses de source, échecs de classement). Invoquée via l'outil Skill par les SKILL.md principales printing-press (Phase 4.85) et printing-press-polish lors de la boucle de diagnostic.

Qu'est-ce que printing-press-output-review ?

Cette sous-compétence interne, `mvanhorn/printing-press-output-review`, est conçue pour effectuer un examen agentique de la sortie échantillonnée d'une CLI imprimée, en identifiant des problèmes de plausibilité que les vérifications basées sur des règles ne peuvent pas gérer, comme la pertinence des correspondances de sous-chaînes, les bugs de format, les suppressions silencieuses de source, ou les échecs de classement. Elle est invoquée automatiquement via l'outil Skill par les SKILL.md principales `printing-press` (Phase 4.85) et `printing-press-polish` pendant la boucle de diagnostic, améliorant la robustesse des processus d'impression en détectant des anomalies subtiles. Cette compétence n'est pas destinée à une invocation directe par l'utilisateur ; ses wrappers actionnables sont `/printing-press` et `/printing-press-polish`, qui l'intègrent dans un flux de travail plus large. Elle cible les plateformes agentiques compatibles avec les SKILL.md de type Claude Code et outils similaires, où l'examen fin de sorties CLI est crucial pour maintenir la qualité et la fiabilité des systèmes automatisés.

Compatible avec✓Claude Code~Codex CLI~Cursor✓Antigravity
npx skills add https://github.com/mvanhorn/cli-printing-press/tree/main/skills/printing-press-output-review

Installed? Explore more Productivité et collaboration skills: steipete/gemini, steipete/gh-issues, steipete/skill-creator · View all 6 →

Demander à votre IA préférée

Ouvre une nouvelle conversation avec cette compétence d'agent déjà préchargée.

Documentation

Que fait printing-press-output-review ?

Sous-compétence interne : examen agentique de la sortie échantillonnée d'une CLI imprimée pour détecter des problèmes de plausibilité que les vérifications basées sur des règles ne peuvent pas encoder (pertinence de correspondance de sous-chaîne, bugs de format, suppressions silencieuses de source, échecs de classement). Invoquée via l'outil Skill par les SKILL.md principales printing-press (Phase 4.85) et printing-press-polish SKILL.md lors de la boucle de diagnostic. Non destinée à une invocation directe par l'utilisateur — ses wrappers actionnables sont /printing-press et /printing-press-polish.

Individual skills in this repo

This repo contains 9 individual skills — each has its own dedicated page.

mvanhorn/printing-press

Generate a ship-ready CLI for an API with a lean research -> generate -> build -> shipcheck loop.

mvanhorn/printing-press-amend

Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally sniff the source site for new endpoints). Confirms scope with the user, plans + executes the fix autonomously, scrubs PII, and opens a PR against mvanhorn/printing-press-library. Two user-in-loop checkpoints: scope after capture, PR draft before open. Trigger phrases: "amend the CLI", "submit a patch", "fix what I just dogfooded", "open a PR for this CLI", "patch this CLI", "add features to my CLI", "rename this command", "add these feeds to <cli>", "sniff for new APIs in <cli>", "amend with these ideas", "use printing-press-amend", "run printing-press-amend".

mvanhorn/printing-press-catalog

Browse and install pre-built Go CLIs for popular APIs from the catalog

mvanhorn/printing-press-import

Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a broken/lost internal copy. Trigger phrases: "import the CLI", "bring it into my library", "fetch from public library", "I don't have it locally yet".

mvanhorn/printing-press-polish

Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use after any /printing-press run, or on any CLI in $PRESS_LIBRARY/. Trigger phrases: "polish", "improve the CLI", "fix verify", "make it publish-ready", "clean up the CLI", "get this ready to ship".

mvanhorn/printing-press-publish

Publish a generated CLI to the printing-press-library repo

mvanhorn/printing-press-reprint

Regenerate an existing printed CLI from scratch under the current Printing Press, with prior research, prior novel features, and prior patches (post-publish hand-fixes) carried into the writing pipeline as reconciliation context rather than dropped on the floor. Pulls the CLI from the public library if it isn't local, recommends reuse-vs-redo of prior research based on age, then hands off to /printing-press with the right context. Use when a machine upgrade would benefit a published CLI more than manual polish. Trigger phrases: "reprint <api>", "regenerate <api>", "redo the <api> CLI", "rebuild <api> from scratch", "this CLI would benefit from a reprint".

mvanhorn/printing-press-retro

Run a retrospective after generating a CLI. Identifies systemic improvements to the Printing Press — templates, Go binary, skill instructions, catalog — so the next CLI comes out better. Creates a GitHub issue with actionable findings when there are Printing Press fixes to make. Use after any /printing-press run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings".

mvanhorn/printing-press-score

Score a generated CLI against the Steinberger bar, compare two CLIs side-by-side

Skills associés