release

Automate software releases with version sync, changelogs, validation, and GitHub publishing.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the entire software release process, from version bumping and changelog generation to validation, tagging, and GitHub release creation, reducing manual effort and potential errors.

Core Features & Use Cases

  • Automated Version Bumping: Syncs version numbers across all necessary files.
  • Changelog Generation: Creates concise changelogs based on git commit history and prefixes.
  • CI/CD Integration: Runs validation scripts and security audits before tagging.
  • GitHub Release Creation: Publishes tagged releases with detailed notes.
  • Use Case: When you're ready to ship a new version of MobiSSH, this skill will automatically update the package.json, generate a changelog from your recent commits, run all tests, perform a security audit, tag the release, and create a GitHub release.

Quick Start

Use the release skill to prepare and tag a new patch version for the project.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate version bumping and changelog generation for GitHub releases?

You can automate GitHub releases by synchronizing version numbers in package.json files and parsing git commit history to generate changelogs. This process reduces manual effort and ensures version consistency across your project before tagging.

Can I run CI/CD validation and security audits before tagging a release?

Yes, you can execute CI validation gates and perform AI-driven security audits using Gemini and Codex before git tagging. This ensures your codebase passes all tests and security checks prior to publishing a GitHub release.

What is the best way to sync version numbers across multiple package.json files during a release?

Syncing version numbers across package.json files is handled automatically during the release process. The automation updates all necessary files to match your target version, eliminating manual file editing and preventing version mismatch errors.

How do I generate a changelog from git commit history automatically?

Changelogs are generated automatically by parsing your git commit history and prefixes. This creates concise release notes based on your recent commits, providing a clear summary of changes for your GitHub release.

Does the automated release process handle closing issues and publishing GitHub releases?

Yes, the automated release process handles git tagging, issue closing, and GitHub release publishing. After validation and security audits pass, it tags the release and publishes it with detailed generated notes.

What are the limitations of automating software releases with AI-driven security audits?

While automation handles versioning, changelog generation, and CI/CD integration, the security audit relies on AI tools like Gemini and Codex. You should still review generated changelogs and audit results to ensure complex edge cases are properly addressed before publishing.