菜单
Use when the user wants to sync docs and then cut a release in one shot. Combines sync-docs → commit → create-release in sequence. Triggers on phrases like "sync docs and release", "sync and cut a release", "update docs and publish a release".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Use when the user says "new issue", "create an issue", "file an issue", "/new-issue", or asks to turn a bug, idea, or discussion into a GitHub issue. Takes an optional description of what the issue should cover; with no input, derives the issue from what was discussed in the current conversation. Verifies claims against the code before filing and produces a complete, complexity-scored issue — never a stub.
Use when the user asks to validate, review, or check whether a GitHub issue is valid. Takes a GitHub issue URL or number (defaults to the latest open issue in the current repo). Verifies every factual claim against the actual code with file:line citations rather than trusting the author's description; for non-trivial proposals, also checks architectural feasibility and proposal self-consistency.
Use when the user asks to validate a GitHub issue with Fable 5, always plan it with Fable 5, and autonomously drive it to a reviewed PR in one shot — "fable-validate-fableplan-loop", "fable validate, fable plan, and work on
Use when the user asks to validate a GitHub issue with Fable 5 and then autonomously drive it to a reviewed PR in one shot — "fable-validate-loop", "fable validate and work on
Required format for creating or editing any GitHub issue — [C<score>] title convention, complexity rationale line, complete-body rule, attribution footer. Load BEFORE creating or editing a GitHub issue.
Use when the user asks to validate a GitHub issue (without Fable), conditionally plan it with fableplan, then autonomously drive it to a reviewed PR in one shot — "validate-fableplan-loop", "validate, plan, and work on
基于 SOC 职业分类
| name | sync-docs-release |
| description | Use when the user wants to sync docs and then cut a release in one shot. Combines sync-docs → commit → create-release in sequence. Triggers on phrases like "sync docs and release", "sync and cut a release", "update docs and publish a release". |
Runs three operations in strict sequence. Do not skip steps or reorder them.
Invoke the sync-docs-runner subagent via the Agent tool:
subagent_type: sync-docs-runnerdescription: Sync docs to recent commitsprompt: Pass through the user's request verbatim plus any session context (target branch, last-sync SHA, specific files, etc.). Do not paste workflow steps into the prompt.model: Omit by default. Override only if the user explicitly names a different LLM.Wait for the agent to return. Relay its summary to the user before proceeding.
After sync-docs completes, commit any doc changes it produced using the Haiku model. Spawn an Agent with model: haiku and the following prompt:
Create a git commit for the doc changes just produced by sync-docs. Steps:
- Run
git statusandgit diffto see all changes.- Run
git log --oneline -10to understand the commit message style used in this repo.- Stage only documentation files changed by sync-docs (CLAUDE.md, AGENTS.md, SKILL.md, README.md, and any other .md files that were modified — never stage .env, secrets, or unrelated files).
- If there is nothing staged after step 3 (nothing changed), skip the commit and report "no doc changes to commit".
- Otherwise, draft a concise commit message focused on the "why" and create the commit:
git commit -m "$(cat <<'EOF'\n<message>\nEOF\n)".- Run
git statusto verify. Do not push.
Wait for the agent to return. Relay its result (commit SHA or "no changes") to the user before proceeding.
Invoke the create-release-runner subagent via the Agent tool:
subagent_type: create-release-runnerdescription: Cut and publish a releaseprompt: Pass through the user's original request verbatim plus any context they provided (target version or bump type, release-notes specifics, etc.). Do not paste workflow steps.model: Omit by default. Override only if the user explicitly names a different LLM.After the agent returns, relay its summary and the release URL to the user.