commit · corezoid — Claude Code skill: what it does, how to install
Automates commits in the corezoid-ai-plugin repository: calculates semver version bumps, updates manifest files, and edits CHANGELOG.md.
MIT ★ 74 updated 2026-10-29
npx skills add corezoid/corezoid-ai-plugin --skill commit -a claude-codeWhat commit does
The skill inspects current modifications using git diff HEAD, git status, and recent commit history. It selects a semver bump level based on what changed: patch for bug fixes or refactoring, minor for new tools or skills, and major for breaking updates.
Next, it synchronizes the "version" field in both plugins/corezoid/.claude-plugin/plugin.json and .claude-plugin/marketplace.json. It also prepends a summary entry to CHANGELOG.md and modifies tables in README.md if skills, MCP tools, or directory structures were added or removed. Finally, it stages modified files and commits them with the configured scope and Co-Authored-By attribution.
This workflow relies directly on the file hierarchy of corezoid-ai-plugin, so running it outside this repository will fail on missing manifest paths.
What it helps with
- bump semver versions across project manifest files
- generate a summary block in
CHANGELOG.md - update skill and MCP tool tables inside
README.md - create a formatted git commit with conventional naming
Example prompts for the agent
- commit changes
- /commit
- make a commit for the new skill
How to install commit
1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill commit -a claude-code2Manually: put the files in place
~/.claude/skills/commit/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/commit/
1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill commit -a codex2Manually: put the files in place
.agents/skills/commit/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill commit -a cursor2Manually: put the files in place
.cursor/skills/commit/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install corezoid/corezoid-ai-plugin .claude/skills/commit2Manually: put the files in place
.github/skills/commit/SKILL.md1Skills CLI (Vercel)
npx skills add corezoid/corezoid-ai-plugin --skill commit -a gemini-cli2Platform CLI
gemini skills install https://github.com/corezoid/corezoid-ai-plugin --path .claude/skills/commitManually: put the files in place
.devin/skills/commit/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about commit
How to install commit in Claude Code?
Run npx skills add corezoid/corezoid-ai-plugin --skill commit -a claude-code.
What does the commit skill do?
It checks the git diff, determines whether to bump patch, minor, or major semver, updates manifest files, documents changes in CHANGELOG.md, and creates the final commit.
Which files does this skill modify when updating versions?
It updates the version field in plugins/corezoid/.claude-plugin/plugin.json and .claude-plugin/marketplace.json.
Source text
SKILL.md · MIT
--- name: commit description: > Project commit helper for corezoid-ai-plugin. Use instead of the generic commit skill whenever the user says "/commit", "commit", "закоммить", "сделай коммит", or asks to commit changes in this repository. --- # Commit with auto version bump This project follows semver. **Every commit must include a version bump** in: - `plugins/corezoid/.claude-plugin/plugin.json` - `.claude-plugin/marketplace.json` ## Step 1 — Inspect changes Run in parallel: - `git diff HEAD` — see what changed - `git status` — see untracked files - `git log -5 --oneline` — see recent commit style ## Step 2 — Determine bump type | Change type | Bump | |---|---| | New feature, new tool, new skill, new node type | **minor** (2.3.x → 2.4.0) | | Bug fix, doc update, text fix, refactor | **patch** (2.3.x → 2.3.x+1) | | Breaking change, major redesign | **major** (2.x.x → 3.0.0) | Read current version from `plugins/corezoid/.claude-plugin/plugin.json`. ## Step 3 — Update versions Update the `"version"` field in **both** files to the new version: - `plugins/corezoid/.claude-plugin/plugin.json` - `.claude-plugin/marketplace.json` ## Step 3.5 — Update CHANGELOG.md Prepend a new entry at the top of `CHANGELOG.md` (right after the `# Changelog` heading) following the existing format: ``` ## [<new_version>] - <bullet summarising what changed — one line per logical change> ``` Derive the bullets from the staged diff: group related changes into a single readable line each. Keep it concise — one sentence per item. ## Step 3.6 — Update README.md Review the diff for changes that affect README content and update the relevant sections in `README.md`: | What changed | What to update in README.md | |---|---| | New or removed skill (`SKILL.md` added/deleted) | **What it does** table — add/remove the row | | New or removed MCP tool | **MCP Tools** table — add/remove the row; **Architecture** code block if the tool group changes | | New plugin directory or top-level file | **Project structure** code block | | Breaking change to install/config | **Installation** or **Configuration** section | If none of the above apply (e.g. pure bug fix, refactor, doc-only change inside an existing skill), skip this step — do not touch README.md. ## Step 4 — Stage and commit Stage all modified files (including the two version files and `CHANGELOG.md`) and create a commit. Follow the project's commit message convention: ``` <type>(<scope>): <short description>, bump to <new_version> ``` Types: `feat`, `fix`, `docs`, `chore`, `refactor` End the commit message with: ``` Co-Authored-By: Claude Sonnet 4.6 <[email protected]> ```
© corezoid · MIT · corezoid/corezoid-ai-plugin
Similar skills
All skills for Git and GitHub →commit by other authors comes first.