trigger-release-build
starsforks
How to install trigger-release-build?
hlnd2t/cs2_vibesignatures/trigger-release-build
$npx -y skills add HLND2T/CS2_VibeSignatures --skill trigger-release-buildSafely dispatch a new release build or same-version republish from the immutable current origin/main SHA. Use only when explicitly asked to publish, rebuild, or republish a game version. Enable trusted legacy snapshot bootstrap only when the user separately and explicitly request
SKILL.md
| 1 | # Trigger Release Build |
| 2 | |
| 3 | Use the bundled script as the only remote-operation entry point. Do not construct an ad-hoc `gh workflow run` |
| 4 | command, accept a user-supplied SHA, move a tag, edit a Release, cancel work, or merge an output PR. |
| 5 | |
| 6 | ## Procedure |
| 7 | |
| 8 | 1. Extract the requested game version, or use `latest` only when the user explicitly asks for the latest version. |
| 9 | 2. Run from any directory: |
| 10 | |
| 11 | ```powershell |
| 12 | uv run python .claude/skills/trigger-release-build/scripts/trigger_release_build.py <GAMEVER-or-latest> |
| 13 | ``` |
| 14 | |
| 15 | Only when the user explicitly requests using the tracked snapshot without an accepted release manifest, append: |
| 16 | |
| 17 | ```powershell |
| 18 | --allow-legacy-bootstrap |
| 19 | ``` |
| 20 | |
| 21 | Do not infer legacy bootstrap from ordinary publish, rebuild, republish, retry, or same-version wording. |
| 22 | |
| 23 | 3. Report the script's selected version, selected mode, legacy-bootstrap state, full `SOURCE_SHA`, commit subject, |
| 24 | and Actions run URL. |
| 25 | 4. If the script refuses the operation, surface its exact safety reason and stop. Do not bypass repository, auth, |
| 26 | version, tag/Release, duplicate-work, or `origin/main` checks. |
| 27 | |
| 28 | The script derives the mode from remote state: use `mode=new` only when both the tag and Release are absent, and use |
| 29 | `mode=republish` only when both exist. Reject mixed states and do not accept a user-supplied mode. Any requested |
| 30 | generator/config change must already be merged into `origin/main`. |
People who liked this also viewed
6 picksType
- microsoft-foundryDeploy, evaluate, fine-tune, and manage Foundry agents end-to-end with azd: hosted agent scaffold/run/deploy, prompt agent create, batch eval, continuous eval, prompt optimizer, Agent Optimizer scaffoSkillsJul 2026
- azure-deployExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application SkillsJul 2026
- azure-preparePrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wSkillsJul 2026
- azure-validate--- name: azure-validate description: "Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity pSkillsJul 2026
- azure-aigatewayConfigure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: semantic caching, token limit, content safety, load balancing, AI model governance, MCP rate limiting, jailbSkillsJul 2026
- azure-hosted-copilot-sdkOfficial agent plugin providing skills and MCP server configurations for Azure scenarios.SkillsJul 2026
