release

Automate GitHub releases for Alt-Tabby with versioning, tests, and compiled assets.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/cwilliams5/Alt-Tabby --skill release-cwilliams5
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/release
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill release-cwilliams5

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of building and publishing new releases for the Alt-Tabby project on GitHub, ensuring a consistent and efficient release workflow.

Core Features & Use Cases

  • Automated Versioning: Determines and updates the project version.
  • Testing & Compilation: Runs the test suite and compiles the executable.
  • Release Notes Generation: Creates release notes based on commit history.
  • GitHub Release Creation: Publishes the release with the compiled executable as an asset.
  • Use Case: A developer can invoke this skill to prepare and push a new version of Alt-Tabby to GitHub, including all necessary build steps and documentation.

Quick Start

Use the release skill to build and publish a new GitHub release for Alt-Tabby.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate GitHub releases with build and test steps?

Automating GitHub releases involves managing versioning, executing test suites, compiling the application, generating notes from git logs, and publishing the tagged release with executable assets via the GitHub CLI.

How are release notes generated from git commit history?

Release notes are generated by extracting commit history from git logs, automatically compiling the changelog entries to document the new version alongside the published executable asset on GitHub.

Do I need PowerShell and GitHub CLI to publish a release?

Yes, publishing a release requires PowerShell, the GitHub CLI (gh), and git installed in your environment to execute the build scripts, manage versioning, and upload the compiled executable as a release asset.

Can I compile an executable and attach it to a GitHub release automatically?

Yes, the build process compiles the application executable and automatically attaches it as a release asset when creating the tagged GitHub release, ensuring the compiled binary is published directly.

What is the best way to manage versioning for a GitHub project release?

Automated versioning determines and updates the project version directly within the build pipeline, ensuring consistent release tagging and tracking before compiling the executable and publishing to GitHub.

Why does my automated GitHub release fail during the build step?

Automated release builds fail when prerequisite tools like git, PowerShell, or the GitHub CLI are missing, or when the test suite encounters errors before the application compilation and release publishing steps.