使い方
- インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
- 必要なツール、認証情報、対応環境を原文で確認します。
- 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/mvanhorn/cli-printing-press --skill printing-press-retro開始前の確認
- 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
- スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
/printing-press-retro
Result: A scrubbed retro document and, when the issue gate passes, GitHub issues for Printing Press defects only.
Next consumer: A maintainer or agent who will change the Printing Press (generator, scorer, skills, or binary) — not the printed CLI that just shipped.
Done: The manuscript proof exists and is scrubbed; every work unit is file-new, comment-on-existing, or local-only; no unredacted secret or PII remains; the user has the outcome list.
Intent: "Raised the floor" is analysis language, not a filing bar. File only when the Printing Press must change to stop a current, reproducible, generalizing P1 or P2 defect. Manual iteration on one CLI is expected work, not a finding. In user-facing output say "the Printing Press"; name the subsystem when pointing at a fix.
Boundaries
- Redact every real secret and PII before quoting. Issue bodies and retro
docs are public. Use references/secret-scrubbing.md Layer 0. Never quote a leaked value as evidence of the leak.
- Don't change the machine by default. The burden of proof is on the finding.
- No P3. File only P1/P2. Anything else is Skip or Drop, not a low-priority
issue. The issue gate files P1/P2 Do work units only.
- Never upload unscrubbed artifacts. Never modify manuscript or library
source trees; scrub copies only.
Authority
Invocation authorizes reading manuscripts/library and writing the retro proof plus scratch copies. It does not authorize GitHub filing or public upload until the user confirms Submit. It does not authorize edits to the printed CLI or to Printing Press source.
Steps
Read references/run-resolution.md first. It resolves $API_NAME, $RUN_ID, $RUN_DIR, $CLI_DIR, and $IN_REPO.
Never execute a phase from memory. When you enter a phase, Read its file from phases/ first.
Follow each file's final Next: pointer. Late procedure lives in the phase file or a role-named reference it loads (references/artifact-packaging.md, references/issue-template.md, references/secret-scrubbing.md). Do not restate those files here.
