release

Orchestrate DOS kernel releases by bumping versions, drafting notes, committing, tagging, and triggering publish.

18|4|Updated Jun 10, 2026

Search Tags:#github actions #release notes #git tags #release automation #semver #version bumping #pypi publishing

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a finished DOS kernel change set into a versioned release, handling the repetitive and error-prone steps of version bumping, release notes, committing, tagging, and publication gating.

Core Features & Use Cases

End-to-end release orchestration: Prepares release context, drafts notes, updates version markers, and creates the release commit.
Safe Git and publish flow: Uses scoped snapshots, race-aware staging, and protected push/tag sequencing to reduce release mistakes.
Repository-specific release hygiene: Covers DOS conventions such as master as trunk, public-repo leak gates, CI verification, and PyPI publish handoff.
Use case: A maintainer has a tested fix or feature ready and wants the assistant to cut a clean release without missing version sync, notes, or pipeline checks.

Quick Start

Ask the release skill to cut a new DOS version from the current branch and follow its prompted release steps.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate Python package release version bumping and PyPI publishing?▼

Automate Python package release by synchronizing semver files, generating release notes, and verifying tagged commits before triggering the PyPI publish pipeline. This orchestrates version bumping and publication gating to ensure a clean, error-free release.

What is the best way to generate release notes and create git tags for a new version?▼

The best way to generate release notes and create git tags is through end-to-end release orchestration that drafts notes, updates version markers, and commits changes with protected tag sequencing. This reduces release mistakes and ensures proper git tag creation.

How do I prevent public repository leaks during git tag and release automation?▼

Prevent public repository leaks during release automation by using public-repo leak gates and race-aware staging. These mechanisms verify CI checks and ensure protected push and tag sequencing before any changes are finalized.

Can I use GitHub Actions to orchestrate semver version bumping and release commits?▼

Yes, you can use GitHub Actions to orchestrate semver version bumping and release commits. The workflow prepares release context, drafts notes, updates version markers, and triggers the publish pipeline with CI witness checks.

How do I handle concurrent edits when cutting a new release branch?▼

Handle concurrent edits during release by using scoped snapshots and race-aware staging within the release flow. This protects against conflicting changes by verifying the tagged commit is eligible and ensuring synchronized semver files before publication.

Why does my release pipeline fail CI verification before PyPI publication?▼

Release pipelines fail CI verification before PyPI publication when the tagged commit is not eligible or CI witness checks detect issues. The release process requires passing these gates to ensure synchronized semver files and safe git tag operations.