Back to Skills

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 re

3,106stars320forksUpdated 6/9/2026

Security Assessment

Safe(100/100)
Security Score100/100

About printing-press-polish

The `printing-press-polish` skill is designed to refine and finalize command-line interfaces (CLIs) generated by the Printing Press system, ensuring they pass verification and are ready for publication. It addresses the common problem of incomplete or error-prone CLI outputs by running a comprehensive set of diagnostics and automatically applying fixes. This eliminates manual post-generation cleanup, reduces developer overhead, and guarantees that the CLI adheres to quality standards before release. By isolating the polishing process in a forked context, it prevents diagnostic noise and iterative changes from affecting the main workflow, providing a clean summary of improvements for the user.

The skill performs a variety of tasks to improve CLI readiness, including running diagnostics such as dogfood, verify, scorecard, go vet, and gosec. It automatically fixes verify failures, static-analysis issues, dead code, missing descriptions, README inconsistencies, and general MCP tool quality concerns. After applying corrections, it reports the before-and-after delta and offers the option to publish the polished CLI. The skill also includes setup instructions for locating the appropriate `cli-printing-press` binary, checking its version against the minimum required version, and handling cases where the target CLI resides in the public library rather than the internal library.

`printing-press-polish` is intended for developers and teams using Printing Press to generate CLIs, particularly those who need to ensure their CLIs meet verification standards or are publish-ready in a single pass. It is useful after any CLI generation run, especially if shipcheck results indicate gaps, verification rates are low, or scorecards fall below acceptable thresholds. Additionally, it can be used standalone on any CLI within the user's press library. This skill is particularly valuable for teams aiming to streamline release processes, maintain high code quality, and reduce manual intervention in CLI preparation.

FAQ

When should I run `printing-press-polish`?

Run this skill after any `/printing-press` generation, especially if the shipcheck verdict is 'ship-with-gaps', the verify pass rate is below 80%, or the scorecard is below 85. It can also be run standalone on any CLI in your `$PRESS_LIBRARY/` to make it publish-ready.

What tools does `printing-press-polish` require?

It requires Bash and the ability to read, write, edit, and grep files. The skill also interacts with the `cli-printing-press` binary and may prompt the user with questions during the polish process.

How do I ensure binary compatibility?

Check that the installed `cli-printing-press` binary meets the minimum version requirement specified in the skill (`min-binary-version: 4.0.0`). Use the binary's version command with JSON output and compare it to the minimum using semantic versioning rules. If the installed version is older, update the binary before running the skill.

Can I polish a CLI from the public library?

Yes, but only after importing it into the internal library. If the CLI is not present in `$PRESS_LIBRARY/<slug>/`, use `/printing-press-import <slug>` first, then run polish. Attempting to polish a CLI not in the internal library will not work.

Does `printing-press-polish` modify my main workspace?

No, the skill runs in a forked context to prevent diagnostic noise, iterative fixes, and re-diagnosis from affecting the main caller. Only a clean summary of improvements is returned.

All Files

4 files
SKILL.md64.7 KB
View
references/publish-turn-boundary.md1.1 KB
View
references/pii-polish.md8.2 KB
View
references/tools-polish.md27.0 KB
View

Install printing-press-polish

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill