stable-release

Promote a shipped DOS rolling release into a stable channel with rollback evidence.

18|4|Updated Jun 10, 2026

Search Tags:#rollback #release #git tags #ci validation #stable channel #evidence file

Ready to run

npx skills add https://github.com/anthony-chaudhary/dos-kernel --skill stable-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stable-release
Source: https://github.com/anthony-chaudhary/dos-kernel/tree/main/.claude/skills/stable-release
Command: npx skills add https://github.com/anthony-chaudhary/dos-kernel --skill stable-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill promotes a DOS kernel release that has already shipped into a named stable channel, creating a provable rollback anchor without rebuilding or bumping versions.

Core Features & Use Cases

Validates the promotion gate with kernel tests, truth verification, CI status, and release age.
Writes a stable release evidence document that captures the exact commit and gate snapshot.
Adds an immutable stable tag on the candidate commit and supports safe re-runs after partial failures.

Quick Start

Ask the Skill to promote the target DOS release and codename, and let it verify the gate, write the evidence file, and tag the approved commit.

Frequently Asked Questions about stable-release

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

FAQPage Schema

How do I promote a DOS rolling release to a stable channel with a rollback anchor?▼

To promote a DOS rolling release to a stable channel, you validate the candidate tag against a green kernel suite, truth syscall, and third-party CI status. The process then applies an immutable stable tag and writes an evidence file without rebuilding the release.

What is a stable release evidence file and why is it needed?▼

A stable release evidence file captures the exact commit and gate snapshot during promotion to a stable channel. It provides a provable rollback anchor and an audit trail, ensuring you can recover cleanly from partial failures without bumping versions.

How do I enforce soak age and CI validation before creating a git tag for a release?▼

Enforcing soak age and CI validation requires checking that the candidate release passes a green kernel suite, a clean truth syscall, and third-party CI status. Once validated, an immutable stable git tag is added to the approved commit.

Can I safely re-run a stable release promotion if the process fails partially?▼

Yes, you can safely re-run the stable release promotion after a partial failure. The process preserves the rolling channel untouched and supports safe re-runs to ensure the immutable stable tag and evidence file are correctly applied.

Does promoting a release to a stable channel require rebuilding or bumping versions?▼

No, promoting a release to a stable channel does not require rebuilding or bumping versions. The process promotes an already shipped DOS rolling release by applying a stable tag and creating a provable rollback anchor.

What are the limitations when adding an immutable stable tag to a candidate commit?▼

Adding an immutable stable tag requires the candidate commit to pass the promotion gate, including soak age enforcement and a clean truth syscall. The operation is limited to releases that have already shipped into a rolling channel.