abandon-staged-release

Name: abandon-staged-release
Author: HLND2T

58stars10forks

How to install abandon-staged-release?

hlnd2t/cs2_vibesignatures/abandon-staged-release

$npx -y skills add HLND2T/CS2_VibeSignatures --skill abandon-staged-release

Installs into the current project.

Summary

Safely discover the unique trusted merged generated-output PR and dispatch the protected recovery workflow for one explicitly identified unpromoted staged release. Use only when the user explicitly asks to abandon or clean a GAMEVER/BUILD_ID, or supplies a trusted GitHub Actions

Files · 1

View on GitHub

SKILL.md

1	# Abandon Staged Release
2
3	Use the bundled script as the only remote-operation entry point. Do not run `cleanup-unmerged`, delete `READY`,
4	remove staging paths manually, accept a user-supplied SHA/path, resume promotion, or trigger a replacement build.
5
6	## Procedure
7
8	1. Require an explicit `GAMEVER/BUILD_ID` or trusted GitHub Actions run/job URL, exact confirmation, and one-line
9	reason. A run URL may identify the staged build itself or a failed release build whose logs uniquely report that
10	staged build as its READY blocker.
11	2. Run from any directory with the build identity:
12
13	```powershell
14	uv run python .claude/skills/abandon-staged-release/scripts/abandon_staged_release.py `
15	<GAMEVER>/<BUILD_ID> `
16	--confirm "ABANDON <GAMEVER>/<BUILD_ID>" `
17	--reason "<WHY_PROMOTION_IS_BEING_ABANDONED>"
18	```
19
20	Or use a run/job URL as independent target evidence:
21
22	```powershell
23	uv run python .claude/skills/abandon-staged-release/scripts/abandon_staged_release.py `
24	<GITHUB_ACTIONS_RUN_OR_JOB_URL> `
25	--confirm "ABANDON <GAMEVER>/<BUILD_ID>" `
26	--reason "<WHY_PROMOTION_IS_BEING_ABANDONED>"
27	```
28
29	3. The script automatically discovers the exact output branch and requires exactly one trusted merged Bot PR from
30	the same repository into `main`; it derives the PR number and head SHA rather than accepting either from the user.
31	Discovery accepts the canonical `gamesymbols/build/<GAMEVER>/<BUILD_ID>` branch and, only for historical recovery,
32	the exact legacy `gamesymbols/<GAMEVER>/build-<BUILD_ID>` branch. All other trust and identity checks remain required.
33	4. Report the target evidence, discovered PR URL, game version/build ID/head SHA, reason, and Actions run URL.
34	5. If the script or workflow refuses the operation, surface the exact safety reason and stop. Never bypass repository,
35	PR author/repository/base/branch, confirmation, active-run, promotion-marker, recovery-path, or index/manifest checks.
36
37	The workflow only removes the matching staged directory and PR index. It refuses any state containing
38	`PROMOTION_STARTED`, `PROMOTED.json`, `PROMOTION_COMPLETE`, or matching accepted-bin incoming/backup paths. It never
39	modifies accepted `bin/<GAMEVER>` and never automatically reruns a release build.

People who liked this also viewed

6 picks

Type

abandon-staged-release

58stars10forks

View on GitHub

How to install abandon-staged-release?

hlnd2t/cs2_vibesignatures/abandon-staged-release

$npx -y skills add HLND2T/CS2_VibeSignatures --skill abandon-staged-release

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Abandon Staged Release
2
3	Use the bundled script as the only remote-operation entry point. Do not run `cleanup-unmerged`, delete `READY`,
4	remove staging paths manually, accept a user-supplied SHA/path, resume promotion, or trigger a replacement build.
5
6	## Procedure
7
8	1. Require an explicit `GAMEVER/BUILD_ID` or trusted GitHub Actions run/job URL, exact confirmation, and one-line
9	reason. A run URL may identify the staged build itself or a failed release build whose logs uniquely report that
10	staged build as its READY blocker.
11	2. Run from any directory with the build identity:
12
13	```powershell
14	uv run python .claude/skills/abandon-staged-release/scripts/abandon_staged_release.py `
15	<GAMEVER>/<BUILD_ID> `
16	--confirm "ABANDON <GAMEVER>/<BUILD_ID>" `
17	--reason "<WHY_PROMOTION_IS_BEING_ABANDONED>"
18	```
19
20	Or use a run/job URL as independent target evidence:
21
22	```powershell
23	uv run python .claude/skills/abandon-staged-release/scripts/abandon_staged_release.py `
24	<GITHUB_ACTIONS_RUN_OR_JOB_URL> `
25	--confirm "ABANDON <GAMEVER>/<BUILD_ID>" `
26	--reason "<WHY_PROMOTION_IS_BEING_ABANDONED>"
27	```
28
29	3. The script automatically discovers the exact output branch and requires exactly one trusted merged Bot PR from
30	the same repository into `main`; it derives the PR number and head SHA rather than accepting either from the user.
31	Discovery accepts the canonical `gamesymbols/build/<GAMEVER>/<BUILD_ID>` branch and, only for historical recovery,
32	the exact legacy `gamesymbols/<GAMEVER>/build-<BUILD_ID>` branch. All other trust and identity checks remain required.
33	4. Report the target evidence, discovered PR URL, game version/build ID/head SHA, reason, and Actions run URL.
34	5. If the script or workflow refuses the operation, surface the exact safety reason and stop. Never bypass repository,
35	PR author/repository/base/branch, confirmation, active-run, promotion-marker, recovery-path, or index/manifest checks.
36
37	The workflow only removes the matching staged directory and PR index. It refuses any state containing
38	`PROMOTION_STARTED`, `PROMOTED.json`, `PROMOTION_COMPLETE`, or matching accepted-bin incoming/backup paths. It never
39	modifies accepted `bin/<GAMEVER>` and never automatically reruns a release build.

People who liked this also viewed

6 picks

Type