release

Automate MobiSSH releases with version bumps, changelogs, and GitHub releases.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/matthewfrazier/mobissh --skill release-matthewfrazier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/matthewfrazier/mobissh/tree/main/.claude/skills/release
Command: npx skills add https://github.com/matthewfrazier/mobissh --skill release-matthewfrazier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end release workflow for MobiSSH, including version bumps, changelog generation from git history, validation, tagging, and GitHub release creation.

Core Features & Use Cases

  • Automates version bumps across all touched files (e.g., server/package.json and public/sw.js) to keep the codebase and client caches in sync.
  • Generates human-readable changelogs from commit history to document changes and improvements between releases.
  • Validates changes, runs pre-release checks, and creates a tagged GitHub release to publish the new version.

Quick Start

Run the release skill to bump versions, generate a changelog, and publish a GitHub release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumps and GitHub release creation from git history?

To automate GitHub release creation and version bumps, this Skill synchronizes version updates across project files, generates changelogs from git history, runs validation checks, and publishes tagged releases.

How do I generate a changelog from git history before publishing a new release?

Generating a changelog from git history is automated during the release workflow, parsing commit messages to document changes between versions before creating the GitHub release.

Can I synchronize version bumps across server package.json and client service worker files?

Yes, synchronizing version bumps across server package.json and client service worker files is supported, keeping server artifacts and client cache versions in sync during the release process.

What is the best way to run pre-release CI validation gates before tagging a release?

Running pre-release CI validation gates before tagging is integrated into the release workflow, validating changes and executing checks automatically before the version is tagged and published.

Does this release automation workflow work for software projects requiring updates across multiple touchpoints?

Release automation for software projects requiring updates across multiple touchpoints is fully supported, synchronizing server and client artifacts while managing changelog generation and tagging workflows.