ss-self-release

Automate version bumping, Git tagging, and pushing to remote repositories.

Updated Feb 14, 2026

Search Tags:#automation #git #ci/cd #versioning #github actions #release

Ready to run

npx skills add https://github.com/JasonLo/skill-sommelier --skill ss-self-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ss-self-release
Source: https://github.com/JasonLo/skill-sommelier/tree/main/skills/ss-self-release
Command: npx skills add https://github.com/JasonLo/skill-sommelier --skill ss-self-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of releasing new versions of your project by automating version bumping, tagging, and pushing, ensuring a consistent and efficient release workflow.

Core Features & Use Cases

Automated Versioning: Automatically suggests version bumps (patch, minor, major) based on commit messages.
Git Tagging & Pushing: Creates annotated Git tags and pushes commits and tags to the remote repository.
Workflow Triggering: Initiates GitHub Actions release workflows upon successful push.
Use Case: After merging a set of features and fixes, you can run this skill to prepare and publish a new release without manually performing each step.

Quick Start

Use the ss-self-release skill to prepare and publish a new version of the project.

Frequently Asked Questions about ss-self-release

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

FAQPage Schema

How do I automate version bumping and Git tagging for a new release?▼

Automating version bumping and Git tagging is handled by analyzing commit history to suggest appropriate version increments and creating annotated Git tags. This ensures a consistent release workflow without manual version management steps.

Can I trigger GitHub Actions release workflows automatically after pushing a new tag?▼

Yes, triggering GitHub Actions release workflows is supported upon successfully pushing commits and tags to the remote repository. This initiates your CI/CD pipelines for deployment automatically as part of the release process.

What preflight checks are needed before automating a software release?▼

Preflight checks for automating a software release include verifying a clean working tree and ensuring synchronization with remote branches. These checks prevent releasing uncommitted changes or divergent code states.

How does automated versioning decide between patch, minor, and major increments?▼

Automated versioning decides between patch, minor, and major increments by analyzing your commit history. It suggests the appropriate version bump based on the nature of the changes recorded in those commits.

Does this release automation work without any external dependencies?▼

Yes, this release automation works without external dependencies. It operates independently using scripts and references to manage versioning, Git operations, and CI/CD pipeline triggering.