release

Automate steer plugin releases with code audit, version bumping, and PR creation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, python, mise, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the release process for steer plugins, ensuring a consistent and reliable release workflow.

Core Features & Use Cases

  • Pre-release Audit: Performs a deep, read-only pre-release audit of the plugin codebase.
  • Version Bumping: Automatically determines and applies the correct semantic version bump.
  • Documentation and Release PR: Ensures that documentation is up-to-date and creates a release PR with appropriate changes.

Quick Start

Run the release skill to cut a new release for the steer plugin.

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 PR creation for plugin releases?

Automating version bumping and PR creation involves running a release process that audits the codebase, applies the correct semantic version bump, validates documentation, and generates a release PR with all changes.

What does a pre-release code audit check in a plugin codebase?

A pre-release code audit performs a deep, read-only review of the plugin codebase to validate codebase integrity and version consistency before cutting a new release.

Do I need git and GitHub CLI installed to automate steer plugin releases?

Yes, automating steer plugin releases requires git, the GitHub CLI (gh), Python, and mise to execute version bumping, validate the codebase, and create release PRs through the GitHub API.

Can I use this release automation for projects other than steer plugins?

This release automation is specifically designed for steer plugins, applying to engineering workflows involving plugin maintenance and release management rather than general-purpose project releases.

How does automated semantic versioning determine the correct version bump?

Automated semantic versioning determines the correct bump by validating version consistency across the codebase during the pre-release audit, then applying the appropriate version increment based on detected changes.

What's the best way to ensure documentation is up-to-date before a plugin release?

The best way to ensure documentation is current before a plugin release is to run an automated release workflow that validates documentation as part of the pre-release audit and includes updates in the release PR.