printing-press-polish

Diagnose and fix generated Go CLIs to pass verification and reach publish-ready state.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Generated CLIs often ship with verification failures, thin MCP tool descriptions, dead code, README gaps, security findings, and customer PII leaks. Manually diagnosing and fixing each class of issue across dogfood, verify, scorecard, go vet, and gosec output is slow and error-prone. ## Core Features & Use Cases - Baseline diagnostics: Runs dogfood, verify, workflow-verify, verify-skill, scorecard with live checks, tools-audit, pii-audit, go vet, and gosec, then parses findings into actionable categories. - Automated fix loop: Fixes verify failures, static-analysis findings, dead code, descriptions, README gaps, and MCP tool quality, then reports the before/after delta. - Publish readiness: Enforces ship gates (verify-skill errors, gosec findings in hand-authored code, publish-validate in standalone mode) and offers to publish when run standalone. - Use Case: After running /printing-press to generate a CLI with a ship-with-gaps verdict, run polish to automatically clear the remaining issues and get the CLI ready to publish. ## Quick Start Ask the assistant to polish the redfin CLI in the printing-press library so it passes verification and is ready to publish.

Frequently Asked Questions about printing-press-polish

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

FAQPage Schema
How do I fix verify failures in a generated Go CLI?

Run the polish skill against the CLI directory; it runs verify, dogfood, and scorecard diagnostics, then automatically fixes failures such as dead code, missing examples, and description gaps. It reports a before/after delta when finished.

How do I improve MCP tool descriptions for a generated CLI?

The tools-audit diagnostic flags empty or thin MCP descriptions. Fixes are written to the mcp-descriptions.json override file and applied with cli-printing-press mcp-sync, since tools-manifest.json and tools.go are generated files that get wiped on regeneration.

What version of cli-printing-press does polish require?

The skill requires cli-printing-press binary version 4.0.0 or newer, checked against the min-binary-version frontmatter field. It also requires a Go toolchain recent enough for the binary, with GOTOOLCHAIN handling for older installs.

Can polish run on a CLI while a build is in progress?

No. Polish checks the build lock status first and refuses to run when an active build holds a lock for that CLI, because polish edits would be overwritten when the build promotes. Stale locks produce a warning but allow polish to proceed.

Why does polish stop before running diagnostics sometimes?

Polish runs a divergence check comparing the internal library copy against the public printing-press-library clone. If the public copy has drifted, it stops and asks whether to sync public changes into internal before proceeding, to avoid overwriting public-only fixes.

Does polish publish the CLI automatically after fixing it?

Only in standalone mode. When invoked as a slash command or with the --standalone flag, polish offers to publish at the end; mid-pipeline invocations from the main printing-press skill defer publishing to the parent flow.