القائمة
Use when the user asks to "create a release", "cut a release", "tag a version", "publish release notes", or ship a new versioned GitHub release for the current repo.
التثبيت باستخدام 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 | create-release |
| description | Use when the user asks to "create a release", "cut a release", "tag a version", "publish release notes", or ship a new versioned GitHub release for the current repo. |
This skill is a dispatch shim. Do not perform the work yourself.
Immediately invoke the create-release-runner subagent via the Agent tool, which runs on Sonnet and contains the full create-release workflow.
Call the Agent tool with:
subagent_type: create-release-runnerdescription: Cut and publish a releaseprompt: Pass through the user's request verbatim, plus any context the user already provided in this session (target version or bump type, whether to bump an in-app version, release-notes specifics, 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 Sonnet via its pinned frontmatter. Override only if the user explicitly names a different LLM when invoking the skill (e.g. "create a release with opus", "/create-release 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 (and the release URL) to the user. Do not re-execute its work.
The full create-release workflow lives in ~/.claude/agents/create-release-runner.md with model: sonnet pinned in frontmatter. Routing through the agent keeps release runs on Sonnet by default — but an explicit user LLM choice overrides it via the Agent tool's model parameter.