release-workflow

graysurf's avatarfrom graysurf

Execute project release workflows by locating and following project-specific RELEASE_GUIDE.md in the repository root or docs/. Use when asked to perform a release, publish a release, cut a tag, run release steps, or when a user references RELEASE_GUIDE.md.

⭐0stars🔀0forks📁View on GitHub🕐Updated Dec 25, 2025
[CI and CD]

When & Why to Use This Skill

The Release Workflow skill automates the end-to-end software publishing process by dynamically locating and executing project-specific instructions within a repository. By strictly adhering to local RELEASE_GUIDE.md files, it ensures that version tagging, build execution, and deployment steps are performed with high precision, reducing manual errors and standardizing the delivery pipeline.

Use Cases

  • Automated Version Tagging: Streamline the process of cutting new Git tags and creating official releases on platforms like GitHub or GitLab by following documented repository protocols.
  • Complex Release Execution: Execute multi-stage publishing workflows that involve running specific scripts, Makefiles, or CI tasks exactly as defined in the project's internal documentation.
  • Release Compliance and Consistency: Ensure every software release follows the exact mandatory steps required by the organization, providing a reliable and auditable deployment history without manual oversight.
namerelease-workflow
descriptionExecute project release workflows by locating and following project-specific RELEASE_GUIDE.md in the repository root or docs/. Use when asked to perform a release, publish a release, cut a tag, run release steps, or when a user references RELEASE_GUIDE.md.

Release Workflow

Contract

Prereqs:

  • Run inside (or have access to) the target repo.
  • rg available on PATH to locate RELEASE_GUIDE.md.
  • 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:

  • Release steps executed exactly per the project’s RELEASE_GUIDE.md, plus release notes/link as provided by the guide.

Exit codes:

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

Failure modes:

  • RELEASE_GUIDE.md missing or multiple guides found (must ask which to use).
  • A guide step fails or is unclear (must stop and follow recovery instructions or ask).

Setup

  • Load commands with source $AGENT_KIT_HOME/scripts/kit-tools.sh

Workflow

  1. Identify the target repository root; ask if the repo path is unclear.
  2. Locate RELEASE_GUIDE.md in the repo root or docs/:
    • Prefer rg --files -g 'RELEASE_GUIDE.md' from the repo root.
    • If multiple guides are found, ask which one to follow.
  3. Read the entire guide before running any commands; do not infer missing steps.
  4. Execute steps in order, using the exact commands and tooling specified (scripts, Makefile, CI tasks, etc.).
  5. Follow the release guide exactly; if anything is unclear, stop and ask rather than making assumptions.
  6. If a step fails, stop and either follow the guide's recovery instructions or ask for user direction.
  7. If no RELEASE_GUIDE.md exists, ask the user for the correct release documentation location.

Output and clarification rules

  • The response must include, in order:
    1. Release content (use the template provided in each project's release guide)
    2. Release link