publish

Automates software release process including merging branches, versioning tagging commits, deploying to production.

27|4|Updated Jun 19, 2025
One-click install
npx skills add https://github.com/markmhendrickson/neotoma --skill publish-markmhendrickson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: publish
Source: https://github.com/markmhendrickson/neotoma/tree/main/.cursor/skills/publish
Command: npx skills add https://github.com/markmhendrickson/neotoma --skill publish-markmhendrickson

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the complex and error-prone process of merging code, versioning releases, tagging commits, and deploying to production, ensuring a consistent and reliable release pipeline.

Core Features & Use Cases

  • Automated Merging: Safely merges development branches into the main branch.
  • Release Versioning: Supports both planned (milestone) and incremental (patch) releases, adhering to semantic versioning.
  • Deployment Automation: Integrates with deployment platforms (like Fly.io) and handles database migrations and smoke tests.
  • Use Case: A software team can trigger a /publish command to automatically merge their latest features, create a new patch version, tag it, and deploy it to their live application, all without manual intervention.

Quick Start

Execute the publish skill to deploy the main repository.

Frequently Asked Questions about publish

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

FAQPage Schema
How do I automate merging branches and deploying to production?

You can automate merging branches and deploying to production by triggering a single command to handle the end-to-end release process. This Skill safely merges development branches and deploys the main repository to live environments.

Does this release automation tool support semantic versioning for patches and major releases?

Yes, this release automation tool supports semantic versioning for both planned milestone releases and incremental patch releases. It automatically versions your releases and tags the corresponding commits in your repository.

Can I use this deployment automation skill with Fly.io and database migrations?

Yes, you can use this deployment automation skill with platforms like Fly.io. It handles database migrations during the release process and runs smoke tests to validate the deployment before completing.

What is the best way to handle rollback if an automated deployment fails?

The best way to handle a failed automated deployment is using the integrated rollback capabilities. This Skill includes validation and testing during the release process to safely revert if issues occur.

How does automated release versioning work with git tagging?

Automated release versioning works by calculating the next semantic version and applying a git tag to the specific commit. This ensures every deployment is traceable back to an exact point in your repository history.