smaqit.release-approval

Validate release version approval via pattern matching or user confirmation.

3|1|Updated Feb 5, 2026

Search Tags:#automation #ci/cd #versioning #release #semver #approval

Ready to run

npx skills add https://github.com/ruifrvaz/smaqit-extensions --skill smaqit-release-approval

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smaqit.release-approval
Source: https://github.com/ruifrvaz/smaqit-extensions/tree/main/.github/skills/smaqit.release-approval
Command: npx skills add https://github.com/ruifrvaz/smaqit-extensions --skill smaqit-release-approval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the release process by automating the verification of suggested release versions, ensuring consistency and preventing errors before deployment.

Core Features & Use Cases

Automated Version Approval: Checks for pre-approval patterns in issues or titles for autonomous workflows.
Interactive User Confirmation: Prompts users for explicit approval or version override in manual workflows.
Version Validation: Ensures the final approved version adheres to semantic versioning standards.
Use Case: Before merging a release branch, this skill can automatically confirm the version if the associated GitHub issue has a specific tag, or it can prompt the release manager for a quick 'yes/no' to proceed.

Quick Start

Use the smaqit.release-approval skill to get approval for the suggested release version v0.6.0.

Frequently Asked Questions about smaqit.release-approval

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

FAQPage Schema

How do I automate release version approval in a CI/CD pipeline?▼

Automate release version approval by configuring pattern matching on issue titles or tags within your CI/CD pipeline. This allows autonomous workflows to validate semantic versioning compliance and proceed without manual intervention.

What is the best way to enforce semantic versioning for release tags?▼

Enforce semantic versioning by validating the suggested release tags and artifacts against semver standards. This verification step ensures versioning compliance and prevents malformed tags from being deployed.

Can I manually override a suggested release version before deployment?▼

Yes, you can manually override a suggested release version during the interactive user confirmation step. This manual workflow prompts the release manager for explicit approval or a version override before proceeding.

Does this release approval workflow support both automated and manual developer workflows?▼

Yes, release approval supports both autonomous CI/CD pipelines and manual developer workflows. It obtains and validates release versions through automated pattern matching or interactive user confirmation based on your configured approach.

Why do I need release version validation before merging a release branch?▼

Release version validation prevents deployment errors by ensuring consistency and semantic versioning compliance. Verifying the suggested version before merging a release branch catches versioning issues early in the process.