commit

Automates version bumps and updates changelogs for simulator-ai-plugin projects.

58|9|Updated May 5, 2026
One-click install
npx skills add https://github.com/corezoid/simulator-ai-plugin --skill commit-corezoid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/corezoid/simulator-ai-plugin/tree/main/.claude/skills/commit
Command: npx skills add https://github.com/corezoid/simulator-ai-plugin --skill commit-corezoid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates version-bump commits for simulator-ai-plugin projects, ensuring release-ready changes and consistent versioning.

Core Features & Use Cases

  • Enforce that every commit includes a version bump in plugin.json and marketplace.json.
  • Automatically update CHANGELOG.md and associated release notes to reflect changes.
  • Provide a standardized commit workflow with a structured message and a co-authored footer for collaboration.

Quick Start

Execute the commit workflow to automatically bump plugin versions during commits.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate version bumps in plugin.json and marketplace.json on git commits?

Automate version bumps on git commits by validating the current version, determining the bump type, and updating plugin.json and marketplace.json. The workflow then stages a compliant commit with a standardized message and co-authored footer.

How does a commit workflow update CHANGELOG.md and release notes for plugin projects?

The commit workflow updates CHANGELOG.md and release notes by detecting changes in plugin configuration files, determining the semantic version increment, and applying the documented changes in a single automated operation.

Do I need to use semver to manage versioning for simulator-ai-plugin projects?

Yes, semantic versioning is required for simulator-ai-plugin projects. The workflow validates the current semver version, automatically determines the correct bump type, and enforces version updates across plugin.json and marketplace.json files.

Can I enforce a co-authored commit message format for version bumps?

Yes, the workflow enforces a standardized commit message format complete with a co-authored footer. It stages all version bump changes and creates a compliant commit to ensure consistent release-ready history.

What is the best way to keep release notes and CHANGELOG.md synced with plugin version changes?

Keep release notes synced by running an automated commit workflow that applies version bumps to plugin.json and marketplace.json while simultaneously updating CHANGELOG.md and associated release notes.

Why does my plugin version commit fail when only one manifest file is updated?

Version bump commits fail if consistency is not maintained. The workflow enforces that every commit includes a version bump in both plugin.json and marketplace.json, validating the current version before staging the final commit.