菜单
Use when syncing closed GitHub issues back into repo docs. Scans closed issues incrementally by updatedAt, reuses a tracked state cache, surfaces only candidates that changed since the last extraction, and records skip/merge/new-doc decisions for this repository.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | issue-doc-sync |
| description | Use when syncing closed GitHub issues back into repo docs. Scans closed issues incrementally by updatedAt, reuses a tracked state cache, surfaces only candidates that changed since the last extraction, and records skip/merge/new-doc decisions for this repository. |
Use this skill when the user asks to:
docs/git pull --ff-only.scripts/issue-doc-sync/review.sh plan.updatedAt against .codex/state/issue-doc-sync/state.json.closedAt, with issue number fallback for same-time ties.scripts/issue-doc-sync/review.sh inspect [issue-number].docs/**/*.md file must keep the visible metadata block under the title:
TypeUpdatedSummarydocs/README.md in the same change.scripts/issue-doc-sync/review.sh record [issue-number] --decision ... --reason ....--issue--decision skip|merge|new-doc--reason--target-doc once per touched doc path when the decision is merge or new-doc.record command now auto-fills issue metadata from GitHub when not provided.record refuses by default and requires --force for an intentional backfill.plan automatically after record.scripts/issue-doc-sync/review.sh plan and confirm unchanged issues disappear from the candidate set.docs/implemented/ for feature-level implemented behaviordocs/general/ only when the conclusion is a longer-lived repo baseline or canonical process.codex/state/issue-doc-sync/state.jsonupdatedAtUse when the user asks for this repository's local upgrade flow: 本地升级, 拉最新代码后升级本地 daemon, upgrade-local.sh, or triggering the built-in local upgrade transaction from a repo build. Prefer the repo helper script and fixed local-upgrade artifact path; do not use the removed install -upgrade-source-binary flag.
Use when handling a GitHub issue for this repository, including raw issue shaping, implementability reassessment, parent/child issue orchestration, durable execution snapshots, product decision-gate handoff, staged execution, result roll-up, and verifier handoff. Run the fixed prepare/lint/finish workflow, keep the issue body current, and stop when the actionable state changed.
Use when creating or revising a page mock, browser-runnable prototype, or interactive demo for this repository's web, setup, onboarding, status, or admin pages, and also when implementing a real product page from an approved mock. Enforces a visible-content contract, final-user-facing content, post-action feedback states, and mock-to-product parity except for real business data and runtime feedback instances inside approved feedback slots.
Use when pushing committed changes from this repository, especially when `git push` may fail because the remote branch advanced. Prefer the repo helper script that fetches, rebases if needed, reruns tests after a successful rebase, and only then pushes.
Independent read-only verification for nearly finished GitHub issue work in this repository. Use when the user asks for 验收, 独立验证, 对齐验证, 完成前复核, or when a medium/large issue needs a separate acceptance pass before closing.
Use when working on this repository's relay stack: Codex app-server protocol translation, relayd, relay-wrapper, Feishu bot integration, VS Code remote integration, or real-stack debugging around /list, /attach, /use, thread routing, helper/internal traffic, and missing Feishu replies. Summarizes the correct execution order, validation steps, and common failure modes specific to this project.