skills.rest
qol-tools
qol-toolsOFFICIAL
Explore all skills by this author →
GitHub

plugin-alt-tab-release-flow

Enforce release commit and tag patterns for plugin-alt-tab CI workflows.

Updated Apr 19, 2026
Search Tags:#automation#git#workflow#release#tagging#ci#commit-messages
One-click install
npx skills add https://github.com/qol-tools/qol-skills --skill plugin-alt-tab-release-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-alt-tab-release-flow
Source: https://github.com/qol-tools/qol-skills/tree/main/plugins/qol-plugin-alt-tab/skills/plugin-alt-tab-release-flow
Command: npx skills add https://github.com/qol-tools/qol-skills --skill plugin-alt-tab-release-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Establishes a repeatable, auditable release process for plugin-alt-tab, preventing inconsistent tagging and wasted CI compute.

Core Features & Use Cases

  • Defines universal commit rules and specific release commit formatting.
  • Enforces CI triggers on main pushes and provides a mechanism to force CI via the ci token in commits.
  • Guides tagging, pre-release checks, and release workflow integration with the release.yml and shared plugin-release workflow.

Quick Start

Create a release tag following the format chore(release): vMAJOR.MINOR.PATCH and push it to the main branch to trigger the release workflow.

Frequently Asked Questions about plugin-alt-tab-release-flow

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

FAQPage Schema
How do I enforce a strict git release commit and tagging format for CI triggers?▼

To enforce a strict git release commit and tagging format, this workflow requires commits to follow the chore(release): vMAJOR.MINOR.PATCH pattern, ensuring tags correctly trigger the release.yml workflow on branch pushes.

What is the correct commit message format to trigger a release workflow on the main branch?▼

The correct commit message format to trigger a release workflow is chore(release): vMAJOR.MINOR.PATCH. Pushing this formatted tag to the main branch initiates the automated release and CI process.

Can I manually force a CI trigger if the automated release workflow does not start?▼

Yes, you can force a CI trigger by including the ci token in your commit messages. This mechanism ensures CI pipelines execute on main pushes even when standard release tag formatting is not used.

How do pre-checks prevent remote ref conflicts before creating a release tag?▼

Pre-checks verify remote refs before creating a release tag to prevent conflicts. By checking the remote repository state prior to tag creation, the workflow avoids inconsistent tagging and wasted CI compute.

Does this release workflow support automated tagging on feature branches or only on the main branch?▼

This release workflow supports automated tagging on both the main branch and feature branches. It applies universal commit rules and specific release commit formatting across these branch scenarios to maintain a repeatable process.

Related Skills

Explore More Software Engineering Skills→
TMI-appsTMI-apps
2

push

Validate and push committed Git changes to a remote repository.

Official
Intermediate
StringKeStringKe
6

release

Automate Cloudflare-Operator release workflows with version bumps, changelogs, Git tags, and GitHub releases.

Community
Advanced
qol-toolsqol-tools

plugin-launcher-release-flow

Enforce release tagging, commit format, and CI triggers for plugin-launcher releases.

Official
Intermediate
NQ-lovecppNQ-lovecpp
6

final-release-review

Audit git diffs from the previous release tag for breaking changes and risks.

Community
Advanced