printing-press-publish
Publish a generated CLI to the printing-press-library repo
Security Assessment
Detected risks:
About printing-press-publish
The printing-press-publish skill publishes a generated CLI from a local library to the printing-press-library repository by creating or updating a pull request. It is designed to handle the final publication stage after CLI generation work has been completed, providing a structured workflow for moving a local CLI into the shared library repository. The skill includes safeguards around invocation context, ensuring that publishing actions are initiated through a direct user request rather than automatically continuing from a previous polish workflow.
Key capabilities include support for publishing by CLI name, handling publish requests originating from a polish workflow through a dedicated marker flag, and managing a controlled live-test bypass mechanism when a specific approved reason is provided. The skill also enforces repository conventions by treating manifest and configuration files as the source of truth and explicitly avoiding edits to generated artifacts that would cause library validation checks to fail. During setup, it validates the required cli-printing-press binary, supports using a local build when operating inside the printing-press repository, and verifies that the publishing environment is correctly configured before proceeding.
This skill is intended for contributors and maintainers working with the printing-press ecosystem who need to submit generated CLIs to the central library repository. Typical use cases include publishing a newly generated CLI, publishing after a polish workflow has completed, updating an existing pull request, or performing publication when certain live-test constraints have been explicitly approved. It is most useful for users who manage CLI integrations and need a repeatable publication process that follows repository rules and validation requirements.
FAQ
How do I publish a generated CLI?
Invoke the skill with a CLI name, such as publishing a specific generated CLI from your local library. A direct user-authored publish request is required.
Can I publish after running a polish workflow?
Yes. A fresh user request that includes the --from-polish flag can be used to indicate a publish action originating from a polish workflow handoff.
Can the live test requirement be skipped?
Only when a non-empty reason is provided through the supported skip-live-test flag. The reason must correspond to approved situations such as authentication unavailability, an upstream outage, or similar concrete operator-approved conditions.
What version requirements exist?
The skill specifies a minimum binary version of 4.0.0 and requires access to the cli-printing-press binary, either from a local repository build or an installed executable.
Are generated library artifacts updated during publishing?
No. The skill explicitly avoids editing generated artifacts such as registry files and generated skill documentation because repository validation checks reject pull requests that modify them.
Install printing-press-publish
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
mvanhorn/cli-printing-press