Release gate batching

Skill idanmann10/vivarium-world/domains/coding/skills/release-gate-batching

Batch focused and full coding gates in a repeatable order before commit.From its SKILL.md

Install

npx -y skills add idanmann10/vivarium-world --skill release-gate-batching

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

0.6 KB, 101 tokens by cl100k_base, as published. Nobody here has run it

Release Gate Batching

Use focused tests to prove the slice, then full gates to prove the repository.

Steps

Run the smallest focused command after implementation.
Run lint, typecheck, tests, and build.
Commit only after the full gate output is read.

Provenance

Seeded during v1 starter-pack expansion from goal.md. Inspired by: https://github.com/obra/superpowers and https://github.com/garrytan/gstack.

What ships with it: 1 file

189 B alongside SKILL.md

lineage.json189 B

Gives 0 of the 12 instructions most ship operate skills give in 101 tokens

Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07

Document a rollback plan before deploymentin 41 of 779, across 22 files
Update the changelogin 21 of 779, across 19 files
Run the test suitein 20 of 779
Create an annotated git tagin 20 of 779
Clean up feature flags after full rolloutin 18 of 779, across 10 files
Verify deployment health after launchin 18 of 779, across 10 files
Test both feature flag statesin 17 of 779, across 9 files
Verify the working tree is cleanin 17 of 779
Make database migrations backward-compatiblein 16 of 779, across 8 files
Set up error monitoring before launchin 15 of 779, across 7 files
Monitor metrics at each rollout stagein 14 of 779, across 5 files
Create a GitHub releasein 14 of 779

Said here and by no other author read

run the smallest focused command after implementation
read the full gate output before committing
use focused tests to prove the slice
use full gates to prove the repository

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.