release

Automate Grok plugin releases with version bumps, tests, tags, npm publish, and GitHub releases.

Updated May 30, 2026
One-click install
npx skills add https://github.com/kwt00/oh-my-grok --skill release-kwt00
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/kwt00/oh-my-grok/tree/main/skills/release
Command: npx skills add https://github.com/kwt00/oh-my-grok --skill release-kwt00

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires npm, git, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the release process for oh-my-grok, reducing manual steps and potential errors.

Core Features & Use Cases

  • Version Bump: Automatically updates version numbers across multiple files.
  • Test Execution: Runs tests to ensure stability before release.
  • Tagging and Pushing: Creates and pushes tags to the repository.
  • Publishing: Publishes the package to npm.
  • GitHub Release: Creates a GitHub release with notes.
  • Use Case: Streamline the release process for oh-my-grok, ensuring all steps are completed accurately and efficiently.

Quick Start

Run the release command with the desired version number: /oh-my-grok:release <version>

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate npm package publishing and git tagging for a plugin release?

Automate npm package publishing and git tagging by running a single release command that bumps version numbers, runs tests, pushes tags, publishes to npm, and creates a GitHub release.

What steps are required to publish a package to npm and create a GitHub release?

Publishing a package to npm and creating a GitHub release requires running tests, updating version numbers, creating and pushing git tags, and generating a GitHub release with notes.

Do I need both git and npm installed to automate version control and package management?

Yes, you need both git and npm installed, because the release automation process relies on git for repository tags and npm for publishing package versions.

How does release automation handle version bumps across project files?

Release automation handles version bumps by automatically updating version numbers across multiple files to ensure consistency before creating git tags and publishing to npm.

Can I run tests before publishing to npm to ensure release stability?

Yes, you can run tests before publishing to npm, because the release workflow executes tests to ensure package stability before proceeding with tagging and publishing.

What is the best way to streamline continuous integration and repository management for npm packages?

Streamline continuous integration and repository management by automating the entire release workflow, which reduces manual steps, prevents errors, and ensures all version control and publishing tasks complete efficiently.