Community코딩 & 개발github.com

mvanhorn/printing-press-publish

생성된 CLI를 printing-press-library 저장소에 게시합니다.

printing-press-publish란 무엇인가요?

이 기술(스킬)은 `mvanhorn/printing-press-publish`로, AI 에이전트가 생성한 CLI(Command Line Interface) 도구를 지정된 `printing-press-library` 저장소에 자동으로 게시할 수 있도록 합니다. 주로 Claude Code, Cursor, Codex와 같은 AI 코딩 어시스턴트 환경에서 사용되며, 개발자의 워크플로우에서 CLI 생성 및 배포 과정을 간소화합니다. 이 스킬은 생성된 CLI 애플리케이션을 패키징하고, 대상 저장소에 푸시하며, 필요한 경우 릴리즈를 트리거하는 자동화된 파이프라인을 제공합니다. 이를 통해 개발자는 반복적인 수동 배포 작업 없이도 AI가 생성한 CLI 도구를 빠르게 공유하고 배포할 수 있어 생산성이 크게 향상됩니다.

지원 대상~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/mvanhorn/cli-printing-press/tree/main/skills/printing-press-publish

Installed? Explore more 코딩 & 개발 skills: steipete/bluebubbles, steipete/eightctl, steipete/blucli · View all 6 →

즐겨 사용하는 AI에게 물어보기

이 에이전트 스킬이 미리 로드된 새 채팅을 엽니다.

문서

printing-press-publish은(는) 무엇을 하나요?

생성된 CLI를 printing-press-library 저장소에 게시합니다.

Individual skills in this repo

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

mvanhorn/printing-press

Generate a ship-ready CLI for an API with a lean research -> generate -> build -> shipcheck loop.

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-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

관련 스킬