菜单
Use when the user asks to sync, update, or refresh CLAUDE.md, AGENTS.md, SKILL.md, and README.md to reflect recent commits or PRs. Triggers on phrases like "sync docs", "update CLAUDE.md", "update AGENTS.md", "update SKILL.md", "update README", "reflect recent changes", or "document the recent PRs".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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
| name | sync-docs |
| description | Use when the user asks to sync, update, or refresh CLAUDE.md, AGENTS.md, SKILL.md, and README.md to reflect recent commits or PRs. Triggers on phrases like "sync docs", "update CLAUDE.md", "update AGENTS.md", "update SKILL.md", "update README", "reflect recent changes", or "document the recent PRs". |
This skill is a dispatch shim. Do not perform the work yourself.
Immediately invoke the sync-docs-runner subagent via the Agent tool, which runs on Opus and contains the full sync-docs workflow.
Call the Agent tool with:
subagent_type: sync-docs-runnerdescription: Sync docs to recent commitsprompt: Pass through the user's request verbatim, plus any context the user already provided in this session (target branch, last-sync SHA, specific files to focus on, etc.). The agent has its own copy of the workflow — do not paste workflow steps into the prompt. Include only the inputs it needs.model: Omit by default — the agent runs on Opus via its pinned frontmatter. Override only if the user explicitly names a different LLM when invoking the skill (e.g. "sync docs with sonnet", "/sync-docs use haiku"). Map the request to the matching model value (opus, sonnet, or haiku) and pass it; the Agent tool's model parameter takes precedence over the agent's frontmatter. Do not infer an override from anything other than an explicit model name.After the agent returns, relay its summary to the user. Do not re-execute its work.
The full sync-docs workflow lives in ~/.claude/agents/sync-docs-runner.md with model: opus pinned in frontmatter. Routing through the agent keeps doc-sync runs on Opus by default — but an explicit user LLM choice overrides it via the Agent tool's model parameter.