Smithery Logo
MCPsSkillsDocsPricing
Login
Smithery Logo

Accelerating the Agent Economy

Resources

DocumentationPrivacy PolicySystem Status

Company

PricingAboutBlog

Connect

© 2026 Smithery. All rights reserved.

    graysurf

    release-workflow

    graysurf/release-workflow
    DevOps
    2

    About

    SKILL.md

    Install

    Install via Skills CLI

    or add to your agent
    • Claude Code
      Claude Code
    • Codex
      Codex
    • OpenClaw
      OpenClaw
    • Cursor
      Cursor
    • Amp
      Amp
    • GitHub Copilot
      GitHub Copilot
    • Gemini CLI
      Gemini CLI
    • Kilo Code
      Kilo Code
    • Junie
      Junie
    • Replit
      Replit
    • Windsurf
      Windsurf
    • Cline
      Cline
    • Continue
      Continue
    • OpenCode
      OpenCode
    • OpenHands
      OpenHands
    • Roo Code
      Roo Code
    • Augment
      Augment
    • Goose
      Goose
    • Trae
      Trae
    • Zencoder
      Zencoder
    • Antigravity
      Antigravity
    ├─
    ├─
    └─

    About

    Execute project release workflows by following a repo-provided release guide when present; otherwise use a changelog-driven fallback flow with helper scripts.

    SKILL.md

    Release Workflow

    Contract

    Prereqs:

    • Run inside (or have access to) the target repo.
    • bash + zsh available on PATH to run helper scripts.
    • git available on PATH (plus any release tooling required by the guide).

    Inputs:

    • The user’s requested release action (tag/release/publish) and the target repository path (if unclear).

    Outputs:

    • Resolve a release guide + template deterministically, then execute the guide steps exactly (no inference).

    Exit codes:

    • N/A (workflow driver; stop and ask on unclear steps)

    Failure modes:

    • Multiple repo guides found (must ask which to use).
    • A guide step fails or is unclear (must stop and follow recovery instructions or ask).
    • Default guide steps fail (must stop and ask how to proceed).

    Workflow

    1. Identify the target repository root; ask if the repo path is unclear.
    2. Resolve the guide + template (project-first; default fallback):
      • $AGENT_HOME/skills/automation/release-workflow/scripts/release-resolve.sh --repo .
      • If it exits 3, stop and ask which guide to use.
    3. Read the resolved guide file fully before running any commands.
    4. Execute the guide steps in order, using the exact commands and tooling specified.
    5. If anything is unclear or a step fails, stop and ask rather than making assumptions.

    Output and clarification rules

    • Use references/ASSISTANT_RESPONSE_TEMPLATE.md when a release is published.
    • Use references/ASSISTANT_RESPONSE_TEMPLATE_BLOCKED.md when blocked (audit/check fails or unclear step).
    • If a release is published, the response must include, in order:
      1. Release content
      2. Release link
    • If blocked (e.g. an audit/check step fails), the response must include:
      1. Failure summary (including audit output when applicable)
      2. A direct question asking how to proceed

    Fallback flow (when no guide exists)

    The default fallback guide lives at:

    • $AGENT_HOME/skills/automation/release-workflow/references/DEFAULT_RELEASE_GUIDE.md

    Entrypoints (fallback helper scripts)

    • $AGENT_HOME/skills/automation/release-workflow/scripts/release-resolve.sh --repo .
    • $AGENT_HOME/skills/automation/release-workflow/scripts/release-publish-from-changelog.sh --repo . --version <vX.Y.Z>
    • Legacy wrapper paths are not supported; keep docs and callers pinned to these scripts.

    Helper scripts (fallback)

    Use only these public entrypoints:

    • Resolve the guide + template deterministically:

      • $AGENT_HOME/skills/automation/release-workflow/scripts/release-resolve.sh --repo .
    • Publish GitHub release from changelog via single entrypoint (extract + audit + upstream-sync check/push + create/edit + verify body):

      $AGENT_HOME/skills/automation/release-workflow/scripts/release-publish-from-changelog.sh --repo . --version v1.3.2 --push-current-branch
      

    Migration notes (removed entrypoints)

    The release-workflow surface was simplified in PR #221. The following entrypoints are deprecated and removed; migrate to the retained commands below.

    Removed entrypoint Replace with
    $AGENT_HOME/skills/automation/release-workflow/scripts/audit-changelog.zsh $AGENT_HOME/skills/automation/release-workflow/scripts/release-publish-from-changelog.sh --repo . --version <tag>
    $AGENT_HOME/skills/automation/release-workflow/scripts/release-audit.sh $AGENT_HOME/skills/automation/release-workflow/scripts/release-publish-from-changelog.sh --repo . --version <tag>
    $AGENT_HOME/skills/automation/release-workflow/scripts/release-find-guide.sh $AGENT_HOME/skills/automation/release-workflow/scripts/release-resolve.sh --repo .
    $AGENT_HOME/skills/automation/release-workflow/scripts/release-notes-from-changelog.sh $AGENT_HOME/skills/automation/release-workflow/scripts/release-publish-from-changelog.sh --repo . --version <tag>
    $AGENT_HOME/skills/automation/release-workflow/scripts/release-scaffold-entry.sh $AGENT_HOME/skills/automation/release-workflow/scripts/release-publish-from-changelog.sh --repo . --version <tag>

    release-resolve.sh remains the guide-resolution entrypoint. release-publish-from-changelog.sh remains the publish entrypoint.

    Related docs

    • Repo-wide script simplification playbook:
      • docs/runbooks/skills/SCRIPT_SIMPLIFICATION_PLAYBOOK.md
    Recommended Servers
    Gitlab
    Gitlab
    GitHub
    GitHub
    Neon
    Neon
    Repository
    graysurf/codex-kit
    Files