release-push

Validate release ZIPs, rename artifacts, generate Slack posts, merge PRs, and tag releases.

3|2|Updated Sep 25, 2025
One-click install
npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill release-push
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-push
Source: https://github.com/oci-ai-incubations/ai-accelerator-starter-packs/tree/main/.claude/skills/archive/old-release-push
Command: npx skills add https://github.com/oci-ai-incubations/ai-accelerator-starter-packs --skill release-push

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-release validation and publishing tasks for software releases: validates release ZIPs for sensitive data, renames artifacts to display-friendly names, generates Slack announcements, merges the release PR, and tags the release after an upgrade completes.

Core Features & Use Cases

  • Post-release validation: checks release artifacts for prohibited content and data leaks; ensures artifacts adhere to naming standards.
  • Artifact management: renames ZIPs to display-friendly names for distribution.
  • Publication automation: generates Slack announcements and merges GitHub release PRs, tagging the version.
  • Use Case: After a release upgrade, run the command to publish and document the release across channels.

Quick Start

Run /release-push v0.0.4 after /release-upgrade to validate, rename, announce, merge, and tag the release.

Frequently Asked Questions about release-push

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

FAQPage Schema
How do I automate post-release validation and publishing for GitHub artifacts?

Automate post-release validation and publishing by validating release ZIPs for sensitive data, renaming artifacts to display-friendly names, generating Slack announcements, merging the GitHub PR, and tagging the version after an upgrade completes.

What is post-release zip validation and why is it needed?

Post-release zip validation checks release artifacts for prohibited content and data leaks before distribution. It ensures artifacts adhere to naming standards, preventing sensitive data from being published in the renamed ZIPs.

How do I generate Slack announcements and merge release PRs automatically?

Generate Slack announcements and merge release PRs automatically by executing the post-release command, which creates Slack posts and handles the GitHub PR workflow merge as part of the tagging process.

Does this release automation workflow require Slack and GitHub integration?

Yes, this release automation workflow requires Slack integration for generating announcements and GitHub PR workflow access for merging PRs and tagging releases across multiple packs.

How do I tag and publish a release after a release upgrade completes?

Tag and publish a release after a release upgrade by running the post-release command, which validates the release_test_matrix, renames ZIPs, merges the PR, and applies versioned release tagging.

What are the limitations of automating release tagging across multiple packs?

Automating release tagging across multiple packs is limited by its dependency on the completion of the release upgrade step, and requires access to the release_test_matrix and zip contents to validate before merging and tagging.