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 tha
Security Assessment
Detected risks:
About printing-press-reprint
The printing-press-reprint skill is designed to regenerate an existing published CLI using the current version of the Printing Press workflow and machine capabilities. It addresses situations where a previously generated CLI would benefit more from a full rebuild than incremental manual improvements. Instead of discarding prior work, the skill preserves and reconciles existing research, novel features, and post-publication patches, carrying them forward as context during regeneration. It can also retrieve a CLI from the public library when a local copy is unavailable and determines whether a reprint is possible based on the availability of published records.
The skill performs several key tasks before initiating regeneration. It resolves CLI identifiers using matching logic that supports API slugs, brand names, legacy naming formats, and approximate matches. It reconciles local and public library presence, importing missing published CLIs when necessary. The workflow compares provenance information from local and public sources, recommends whether prior research should be reused or redone, and prepares context for the downstream printing process. An important capability is the structured reconciliation of previously introduced features, ensuring they are explicitly evaluated and either retained, reframed, or removed with documented reasoning rather than being silently carried forward.
This skill is intended for users maintaining or evolving generated CLIs after significant Printing Press changes, such as new transport mechanisms, authentication modes, MCP capabilities, or scoring criteria. It is useful when a published CLI has known systemic limitations or when existing feature decisions should be reconsidered under updated tooling and user personas. Developers and maintainers responsible for keeping generated CLIs aligned with current platform capabilities are the primary audience.
FAQ
When should I use printing-press-reprint instead of a polishing workflow?
Use it when a CLI would benefit from a complete regeneration due to significant Printing Press changes or systemic issues. For isolated code-quality fixes, a polishing workflow is preferred.
Can the skill work if the CLI is not available locally?
Yes. If the CLI exists in the public library but not locally, the skill imports it and continues the reprint process.
What CLI identifiers are supported?
The skill can resolve API slugs, brand names, legacy <api>-pp-cli formats, and close matches using its registry-based resolution process.
How are previous features handled during regeneration?
Prior research, novel features, and patches are passed into the regeneration pipeline as reconciliation context so they can be reviewed, retained, reframed, or removed with explicit reasoning.
What happens if neither a local nor public version of the CLI exists?
The reprint process stops and recommends creating a fresh CLI using the standard printing workflow instead.
Install printing-press-reprint
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
mvanhorn/cli-printing-press