XerahS Release Bump Tag

Overview

Use this skill to run release steps in strict order:

• Step 1: Execute maintenance prep first (git pull --recurse-submodules and git submodule update --init --recursive)
• Step 2: Run .ai/skills/update-changelog/SKILL.md second (optional only if docs/CHANGELOG.md is intentionally absent)
• Step 3: Verify build, then execute bump/commit/push/tag automation
• Step 4: Monitor the tag-triggered release workflow every 2 minutes
• Step 5: If failure occurs, inspect logs, fix issues, and retry with the next patch version
• Step 6: Ensure standard release notes block is present on the GitHub release
• Step 7: Set the successful release as pre-release by default (opt out only when intentionally publishing stable)

Repository target behavior:

• The automation is repository-agnostic. Git pushes use the local origin remote.
• GitHub CLI operations (gh run, gh release) resolve the target from the GitHub origin remote by default, for example ShareX/XerahS or KovaForge/XerahS.
• Use --repo owner/name to override the inferred target when needed.