printing-press-publish

Publishes a generated CLI to the printing-press-library GitHub repository as a pull request.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Publishing a generated CLI to the public printing-press-library repository involves forking, cloning, validating, live-testing, packaging, and opening a compliant pull request — a long, error-prone sequence where a single wrong file edit (like touching bot-regenerated registry files) gets the PR auto-rejected. This Skill automates the entire publish flow with the correct guards and conventions. ## Core Features & Use Cases - End-to-end publish pipeline: Resolves the CLI by name, confirms its category, runs structural validation and a live end-to-end dogfood gate, then packages and opens a PR against mvanhorn/printing-press-library. - Registry safety guards: Never edits bot-regenerated files (registry.json, README catalog cells, cli-skills mirrors) that would hard-fail the library's CI, and preserves release-ledger files when replacing an existing CLI. - Blocked API journal mode: With --blocked-api-journal, records a held generation attempt in blocked-apis.json as a journal-only PR instead of publishing a CLI. - Use Case: After generating and polishing a Notion CLI with Printing Press, run the publish skill to validate it against the live API, fork the library repo, push a branch, and open a Greptile-review-ready pull request. ## Quick Start Ask the assistant to publish the notion CLI to the printing-press-library repository as a pull request using this skill.

Frequently Asked Questions about printing-press-publish

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

FAQPage Schema
How do I publish a generated CLI to the printing-press-library repo?

Invoke the skill with the CLI name, for example /printing-press-publish notion. It resolves the API slug, confirms the category, runs validation and a live end-to-end gate, then forks or clones the library repo, pushes a branch, and opens a pull request.

What files must a publish PR not touch in printing-press-library?

Publish PRs must not edit registry.json, README catalog cells, or cli-skills/pp-*/SKILL.md, because the library regenerates them post-merge and its verify-library-conventions workflow hard-fails any PR that changes them. Release-ledger files like CHANGELOG.md are also assigned by the library after merge.

Can I skip the live test when publishing a CLI?

Yes, only with --skip-live-test=<reason> for concrete cases like auth-unavailable, a known upstream outage, or LAN-unreachable hardware APIs. The skill writes a phase5-skip.json marker with the reason and source fingerprint instead of running the live dogfood gate.

Why does publish fail with a phase5 fingerprint mismatch?

The Phase 5 acceptance marker is bound to the source tree it was generated from; any .go edit after it was written invalidates it. Re-run the live gate in Step 4.5 to write a fresh marker into both the embedded and archived proofs directories before packaging.

What is blocked API journal mode and when is it used?

Blocked API journal mode, triggered by --blocked-api-journal, records a held generation attempt in the library's blocked-apis.json file as a journal-only PR. It is used when an API cannot be generated due to a repeatable blocker, so future runs warn before retrying.

What prerequisites does the publish skill require?

It requires the cli-printing-press binary at v4.0.0 or newer, an authenticated GitHub CLI (gh auth login), a Go toolchain recent enough for the binary, and sufficient disk space. Setup stops with an error if any of these are missing.