doc-publish
Use when a document for people to read (README, dev-log, design write-up, release notes) is being taken all the way out — flipped from draft to published, or pushed — or when the user says "publish this doc", 收尾, 发出去, or asks whether a draft is ready to push.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 76
- Forks
- 17
01 前言 Front Matter
- name
- doc-publish
- description
- Use when a document for people to read (README, dev-log, design write-up, release notes) is being taken all the way out — flipped from draft to published, or pushed — or when the user says "publish this doc", 收尾, 发出去, or asks whether a draft is ready to push.
02 资源文件 2
- 其他precheck.conf.example193 B
- 脚本precheck.sh2.3 KB
03 SKILL.md 正文
doc-publish
Runs the finishing pipeline. Each stage is its own skill; this one decides which stages run, in what order, and when pushing is allowed.
doc-fact-check— claims against code, PRs, migrationsdoc-polish— wordingdoc-review— final gate, by a different model
Which stages
| Situation | Run |
|---|---|
| Staying a draft | fact-check only |
| Going to published | fact-check → polish → review |
| A draft whose content is all live, with nothing pending | all three in one go, still in order |
Drafts often describe work that has not shipped yet. Polishing them early is wasted when the facts move.
Order: serial
Never run polish and review in parallel: review reads the polished text.
Push
{{PRECHECK_PATH}} <file.md>
{{PUBLISH_CMD}}
git push
Push only after doc-review returned SHIP.
Red flags
- "It's short, just push it." → Length does not change the stages.
- "I'll fact-check it myself." → The author remembers the narrative, not the source.
- "Subagents aren't allowed here, so I'll self-review." → Ask the user for permission. Never replace stage 1 or 3 with self-review; stage 3 exists to switch models.
- "Polish and review together saves time." → Review reads the polished text.
- "A subagent says this is wrong, I'll change it." → When a finding conflicts with your source, verify it yourself first.
- "The blocker is small, I'll fix it after pushing." → Blockers go to zero before the push.
04 同仓库更多 Skills
doc-review
Use when reviewing docs in this repo (team version).
zh-hant-converter
Use when Simplified Chinese text needs a Traditional Chinese version — internal team docs converted with opencc s2hk, or a product's Simplified Chinese UI copy mirrored into its Traditional Chinese locale — or when the user says 转繁, 同步繁体, or "convert to zh-Hant".
cleaning-dev-caches
Use when this Mac's disk is nearly full, or the user asks to clear re-downloadable caches (「清缓存」「硬盘满了」, "clear caches") — Homebrew, npm / pnpm / yarn / bun / uv / pip, Gradle, Playwright browsers, Edge and VS Code updater caches, simulator dyld caches, unused Rust toolchains. Not for build output (cleaning-dev-build-artifacts) or personal files.
cleaning-dev-build-artifacts
Use when this Mac's disk is nearly full, or the user asks to clean build output — Rust target/ dirs or Claude Code worktrees (.claude/worktrees) under {{DEV_ROOT}} (「清编译产物」「清 target」「清 worktree」「硬盘满了」, "clean build artifacts"). Not for package-manager or app caches (cleaning-dev-caches) or personal files.
ios-keyboard-page-shift
Use when, on iPhone Safari or an iOS WebView, a page or a full-screen app shell (top bar, scrolling list, bottom input) moves up when a text field is focused and stays up after the keyboard closes, leaving the top bar off-screen, the input mid-screen and an empty band below it, or when an earlier fix for that symptom did not hold.
codex-review
Use when the user asks to review a branch, PR or diff with codex ("review this with codex", 用 codex 审一下, "codex review PR N"). Runs `codex exec` from the shell with a hand-written, repo-aware prompt; falls back to one OpenRouter GPT call only when codex is out of quota. Covers the invocation contract and the failure modes that make codex look dead or silently produce no report.