Community研究與資料分析github.com

mvanhorn/printing-press

透過精簡的研究 -> 生成 -> 建置 -> 上線檢查流程,為 API 產生一個可立即上線的 CLI。

printing-press 是什麼?

這個技能旨在幫助開發者快速為 API 建立一個可直接部署的 CLI 工具。它遵循一個精簡的四階段流程:研究(Research)階段分析 API 規格、生成(Generate)階段自動產生 CLI 程式碼、建置(Build)階段編譯與測試、上線檢查(Shipcheck)階段確保符合發布標準。支援多種主流 AI 代理平台如 Claude Code、Cursor 和 Codex。透過自動化產生 CLI,開發者能節省大量手動編寫程式碼的時間,並確保產出的 CLI 遵循業界最佳實務,包含錯誤處理、文件說明與參數驗證。

相容平台~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/mvanhorn/cli-printing-press/tree/main/skills/printing-press

Installed? Explore more 研究與資料分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →

在你喜歡的 AI 中提問

開啟一個已預先載入此 Agent Skill 的新對話。

說明文件

printing-press 是做什麼的?

透過精簡的研究 -> 生成 -> 建置 -> 上線檢查流程,為 API 產生一個可立即上線的 CLI。

概述

這個工具能自動化 CLI 的產生流程,讓你專注於 API 的業務邏輯,而不是重複的 CLI 樣板程式碼。

運作方式

  1. 研究 (Research) - 分析 API 端點、參數與回應格式
  2. 生成 (Generate) - 根據研究結果自動產生 CLI 程式碼
  3. 建置 (Build) - 編譯與測試 CLI 以確保運作正常
  4. 上線檢查 (Shipcheck) - 執行品質檢查以確保 CLI 符合發布標準

支援平台

  • Claude Code
  • Cursor
  • Codex
  • 其他 AI 代理平台

使用方法

# 開始為 API 產生 CLI
printing-press generate --api <api-spec>

# 建置 CLI
printing-press build

# 執行上線檢查
printing-press shipcheck

設定

你可以在專案根目錄建立 printing-press.config.json 來設定 CLI 產生的選項:

{
  "name": "my-cli",
  "version": "1.0.0",
  "language": "python",
  "output": "./cli"
}

進階選項

  • --language:指定 CLI 的程式語言(python、node、go 等)
  • --output:指定輸出目錄
  • --template:使用自訂範本

貢獻

歡迎提交 issue 或 pull request。請確保通過所有測試並遵循程式碼風格指南。

授權

MIT

Individual skills in this repo

This repo contains 9 individual skills — each has its own dedicated page.

mvanhorn/printing-press-amend

Amend a published CLI from one of two input sources: (1) dogfood mode mines the active Claude Code session transcript for friction (missing flags, hand- rolled API payloads, silent-null returns); (2) direct-input mode accepts user-supplied asks (rename a command, add commands or feeds, fix a named bug, optionally sniff the source site for new endpoints). Confirms scope with the user, plans + executes the fix autonomously, scrubs PII, and opens a PR against mvanhorn/printing-press-library. Two user-in-loop checkpoints: scope after capture, PR draft before open. Trigger phrases: "amend the CLI", "submit a patch", "fix what I just dogfooded", "open a PR for this CLI", "patch this CLI", "add features to my CLI", "rename this command", "add these feeds to <cli>", "sniff for new APIs in <cli>", "amend with these ideas", "use printing-press-amend", "run printing-press-amend".

mvanhorn/printing-press-catalog

Browse and install pre-built Go CLIs for popular APIs from the catalog

mvanhorn/printing-press-import

Bring a published CLI from the public library into the internal library so it's identical to a freshly-generated copy — module path reverted, manuscripts placed alongside, ready for /printing-press-polish or /printing-press-emboss. Use when the public library has a CLI you don't have locally, or to recover from a broken/lost internal copy. Trigger phrases: "import the CLI", "bring it into my library", "fetch from public library", "I don't have it locally yet".

mvanhorn/printing-press-output-review

Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by main printing-press SKILL.md (Phase 4.85) and printing-press-polish SKILL.md during the diagnostic loop. Not for direct user invocation — its actionable wrappers are /printing-press and /printing-press-polish.

mvanhorn/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 ready to ship".

mvanhorn/printing-press-publish

Publish a generated CLI to the printing-press-library repo

mvanhorn/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 than manual polish. Trigger phrases: "reprint <api>", "regenerate <api>", "redo the <api> CLI", "rebuild <api> from scratch", "this CLI would benefit from a reprint".

mvanhorn/printing-press-retro

Run a retrospective after generating a CLI. Identifies systemic improvements to the Printing Press — templates, Go binary, skill instructions, catalog — so the next CLI comes out better. Creates a GitHub issue with actionable findings when there are Printing Press fixes to make. Use after any /printing-press run. Trigger phrases: "retro", "retrospective", "what went wrong", "improve the press", "post-mortem", "lessons learned", "what can we improve", "file a retro", "submit findings".

mvanhorn/printing-press-score

Score a generated CLI against the Steinberger bar, compare two CLIs side-by-side

相關技能