skills.rest
barkleesanders
barkleesandersCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

printing-press-polish

Diagnose and fix Go CLI quality issues for public library publication.

5|Updated Mar 27, 2026
Search Tags:#code quality#static analysis#verification#publish readiness#cli polishing#go cli#mcp tool quality
One-click install
npx skills add https://github.com/barkleesanders/claude-code-starter --skill printing-press-polish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: printing-press-polish
Source: https://github.com/barkleesanders/claude-code-starter/tree/main/skills/printing-press-polish
Command: npx skills add https://github.com/barkleesanders/claude-code-starter --skill printing-press-polish

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Generated CLIs from the Printing Press toolchain often fail verification, have static analysis issues, dead code, README gaps, or low-quality MCP tool descriptions that block publication. This skill eliminates manual cleanup work by automatically diagnosing and fixing all quality gaps to make a CLI publish-ready in one pass.

Core Features & Use Cases

  • Automated Diagnostic Runs: Executes dogfood, verify, scorecard, go vet, gosec, PII audit, and MCP tool quality checks to surface all issues in a single pass.
  • Automatic Issue Resolution: Fixes verify failures, static analysis findings, dead code, stale files, description gaps, README issues, and MCP tool quality problems without manual intervention.
  • Pre-Publish Validation: Runs publish-validate gates for standalone invocations, reports before/after deltas, and offers to publish the cleaned CLI to the public library.
  • Use Case: After running /printing-press to generate a new CLI, or when working with an existing CLI in your Printing Press library, run this skill to resolve all quality gaps and prepare the CLI for public release.

Quick Start

Use the printing-press-polish skill to automatically fix all verification failures, static analysis issues, and quality gaps on your generated CLI so it 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 verification failures and go vet errors in a generated Go CLI?▼

To fix verification failures and go vet errors in a generated Go CLI, run an automated diagnostic and resolution pass. This surfaces static analysis findings, dead code, and quality gaps, automatically applying fixes to make the CLI publish-ready.

What is publish readiness for a Go CLI and what checks are required?▼

Publish readiness for a Go CLI means passing all quality gates required for public library publication. Required checks include dogfood, verify, scorecard, go vet, gosec, PII audit, and MCP tool quality validation to ensure the code meets public release standards.

How do I automate code quality and static analysis fixes for a Go CLI before release?▼

Automate code quality and static analysis fixes for a Go CLI by running a pre-publish validation tool. It executes diagnostic runs for issues like dead code and stale files, automatically resolving findings without manual intervention to prepare the CLI for publication.

Can I use an automated polishing tool on an existing Go CLI in my library?▼

Yes, you can use an automated polishing tool on an existing Go CLI in your internal library. It coordinates diagnostic runs and automated issue resolution for existing projects, applying pre-publish validation gates to clean and prepare them for public release.

Why does my generated Go CLI fail publication checks after creation?▼

Generated Go CLIs often fail publication checks due to static analysis issues, dead code, README gaps, or low-quality MCP tool descriptions. These quality gaps block publication and require automated diagnostic runs and issue resolution to achieve publish readiness.

Related Skills

Explore More Software Engineering Skills→
agentclashagentclash
25

go

Detect Go modules and run the test suite after code changes.

Official
Basic
VledicFrancoVledicFranco

pre-publish-qa

Run pre-publish QA checks for npm packages with builds, tests, and health gates.

Community
Advanced
barkleesandersbarkleesanders
5

printing-press-reprint

Regenerate published CLIs while preserving research, custom features, and patches.

Community
Advanced
cdalsoniiicdalsoniii

SAST Triage

Triage gosec, golangci-lint, and govulncheck findings by severity and false positives.

Community
Intermediate