release

Automates versioned releases by running validation gates, bumping versions, building artifacts, and pushing commits.

Updated Aug 21, 2025
One-click install
npx skills add https://github.com/Adithiya-S/AI-Study-Companion --skill release-adithiya-s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/Adithiya-S/AI-Study-Companion/tree/main/.agents/skills/release
Command: npx skills add https://github.com/Adithiya-S/AI-Study-Companion --skill release-adithiya-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Releasing a plugin manually involves many error-prone steps: running typechecks and tests, bumping the version, rebuilding artifacts, and crafting a proper commit. This Skill orchestrates the entire release workflow so nothing is skipped or done out of order. ## Core Features & Use Cases - Pre-flight Gates: Runs typecheck, tests, and manifest validation in parallel and halts the release if any gate fails. - Guided Version Bumping: Reads the version from .plugin/plugin.json and applies semver rules (patch/minor/major) based on the type of change. - Artifact Rebuild & Commit: Rebuilds compiled hooks and the skill manifest, then stages, commits with the conventional message format, and pushes to main. - Use Case: After merging a new feature, ask the assistant to cut a minor release; it validates everything, bumps the version, rebuilds, and pushes a properly formatted commit. ## Quick Start Ask the assistant to release the plugin with a patch version bump and push it to main.

Frequently Asked Questions about release

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

FAQPage Schema
How do I release a new version of a plugin with automated checks?

Invoke the release workflow, which runs typecheck, tests, and manifest validation in parallel before bumping the version in plugin.json, rebuilding artifacts, and pushing a commit. The process stops immediately if any gate fails.

How do I decide between patch, minor, and major version bumps?

Use patch for bug fixes, test updates, and docs; minor for new skills, hooks, or features; and major for breaking changes to the hook API or skill map. If unspecified, the workflow defaults to a patch bump.

Where is the version number stored for this plugin?

The single source of truth is the version field in .plugin/plugin.json. There is no package.json version to keep in sync, so only that one file needs updating during a release.

What happens if the pre-commit hook fails during a release?

The pre-commit hook re-runs typecheck and recompiles hooks automatically. If it fails, fix the underlying issue and create a new commit rather than amending the existing one.

Can I skip the validation gates to release faster?

No. The workflow explicitly stops if typecheck, tests, or validation fail, requiring you to fix issues before proceeding. This prevents broken artifacts from being committed and pushed.