skills.rest
chanhee-kang
chanhee-kangCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

auto-deploy

Automate oh-my-gemini deployment to npm and GitHub releases.

2|Updated Feb 3, 2026
Search Tags:#automation#versioning#npm#GitHub#release#deploy
One-click install
npx skills add https://github.com/chanhee-kang/oh-my-gemini --skill auto-deploy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-deploy
Source: https://github.com/chanhee-kang/oh-my-gemini/tree/main/skills/auto-deploy
Command: npx skills add https://github.com/chanhee-kang/oh-my-gemini --skill auto-deploy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the end-to-end deployment workflow for oh-my-gemini, removing manual steps and reducing release friction.

Core Features & Use Cases

  • One-click deployment: Build, test, publish to npm, and create a GitHub release with a single trigger.
  • Version management: Automatically determine semantic versioning based on changes.
  • Release automation: Tag releases, push changes, and trigger CI workflows.

Quick Start

Use the Gemini CLI to deploy a new release. Example:

/oh-my-gemini:auto-deploy --dry-run /oh-my-gemini:auto-deploy --version 0.1.2

Frequently Asked Questions about auto-deploy

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

FAQPage Schema
How do I automate npm and GitHub releases in a CI/CD pipeline?▼

Automating npm and GitHub releases involves handling version bumps, builds, tests, publishing, and tagging within a CI/CD pipeline. This skill triggers these end-to-end release workflows automatically to remove manual deployment friction.

How do I determine semantic versioning automatically before publishing to npm?▼

Semantic versioning is determined automatically based on repository changes. During the deployment workflow, the system analyzes commits to apply the correct version bump before publishing to npm and tagging GitHub releases.

Do I need a GitHub token and Git access to automate deployment?▼

Yes, Git access and a GitHub token are required to automate deployment. The workflow needs these credentials to push changes, tag releases, and trigger CI workflows on GitHub, alongside requiring Node.js and npm installed.

Can I test a deployment workflow without actually publishing to npm?▼

Yes, you can test deployment without publishing using the optional dry-run mode. Executing the deployment command with the dry-run flag validates the build, test, and version bump steps without pushing changes or releasing packages.

What is the best way to handle end-to-end release workflows for Node.js packages?▼

The best way to handle end-to-end Node.js release workflows is automating the entire sequence: version bumping, building, testing, npm publishing, and GitHub tagging. This removes manual steps and ensures consistent release automation.

Related Skills

Explore More Software Engineering Skills→
ragnarokhaaragnarokhaa
4

github-auth

Automate GitHub authentication setup using git and gh CLI methods.

Community
Advanced
sachinnair90sachinnair90

release-process

Coordinate safe software releases with semver, Git tags, GitHub Releases, and npm publication.

Community
Advanced
Fantasia1999Fantasia1999

changelog-generator

Generate changelog entries from Conventional Commits in Markdown or JSON formats.

Community
Advanced
JacksonZx535JacksonZx535

ship

Automate software release workflows with Git and GitHub PR creation.

Community
Advanced