verify-printing-press

Installation
SKILL.md

Verify the Printing Press

The product surface is a CLI that produces other CLIs. A user runs cli-printing-press generate on a spec and gets a printed CLI: <api>-pp-cli, plus <api>-pp-mcp for agents. Proving a change means printing a CLI and then driving what was printed. The four surfaces, in order of how often a change touches them:

  1. cli-printing-press generate (spec → printed CLI tree, with 9 quality gates)
  2. The printed CLI's commands against an API
  3. The printed MCP server's tools and annotations
  4. The press's verifiers run on a printed CLI (verify, verify-skill, scorecard, shipcheck, dogfood)

Everything goes through scripts/pp-verify (paths below are relative to this skill directory). It never touches the real ~/printing-press or the real config of a printed CLI. Each run gets its own decoy HOME, output dir, mock port, and evidence directory, so two runs can go side by side. Every drive in this skill uses the fixture testdata/golden/fixtures/golden-api.yaml, which prints printing-press-golden-pp-cli with env prefix PRINTING_PRESS_GOLDEN_.

This skill complements scripts/golden.sh verify, scripts/verify-generator-output.sh, and go test ./.... Those prove bytes and compilation. This skill proves behavior: what the printed binary actually sends, refuses, and reports.

Launch

.agents/skills/verify-printing-press/scripts/pp-verify launch
Installs
1
GitHub Stars
5.0K
First Seen
Today