release

Automate release coordination with version tagging, changelog generation, and GitHub publication.

2|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Wilder1222/superomni --skill release-wilder1222
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Wilder1222/superomni/tree/main/skills/release
Command: npx skills add https://github.com/Wilder1222/superomni --skill release-wilder1222

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Combined RELEASE stage coordinates a ship workflow and retrospective in a single artifact, reducing coordination overhead and ensuring consistent release artifacts.

Core Features & Use Cases

  • Parallel release workflow and retrospective generation.
  • Trigger signals: "/release", "release", "ship and reflect", "end sprint".
  • Automated status reporting, environment checks, version tagging, changelog updates, and release publication.

Quick Start

Trigger the release workflow to ship code and capture a retrospective in one artifact.

Frequently Asked Questions about release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate sprint release notes and version tagging in one workflow?▼

Sprint release automation combines ship workflow and retrospective generation into a single artifact, automatically handling version tagging, changelog updates, and GitHub release publication to reduce coordination overhead.

What's the best way to combine a GitHub release publication with a post-release retrospective?▼

Combining a GitHub release publication with a retrospective captures both deployment artifacts and post-release analysis together, ensuring synchronized release notes and environment checks while generating a unified retrospective artifact.

Does automated CI/CD release coordination support sprint-based project pipelines?▼

Automated CI/CD release coordination explicitly supports sprint-based software teams and project pipelines requiring synchronized release notes, version bumps, environment checks, and tagging.

How do I trigger an end-of-sprint ship and reflect workflow for automated status reporting?▼

Trigger an end-of-sprint ship and reflect workflow using signals like /release, ship and reflect, or end sprint to automate status reporting, version bumps, and changelog generation.

Can I generate changelog updates and perform version bumps without manual intervention?▼

Changelog updates and version bumps are fully automated during the release workflow, applying environment checks and version tagging before GitHub release publication without manual intervention.

When should I use a combined release and retrospective workflow over separate deployment steps?▼

Use a combined release and retrospective workflow over separate steps when sprint-based teams need synchronized release artifacts, reducing coordination overhead between deployment and post-release analysis.