ci: require plugin version bump for any plugin change

[myasnikovdaniil]

Summary

PR #9 changed skills/cozystack-upgrade/SKILL.md without bumping plugin.json .version, and nothing in CI caught it. This adds an automated check so the same gap doesn't recur.

• .github/workflows/check-plugin-version-bump.yml — on PRs touching agents/, hooks/, mcp/, or skills/, asserts that every modified plugin's .claude-plugin/plugin.json .version is strictly greater (by sort -V) than on the base branch. New plugins (no manifest on base) are exempted. Failures emit a ::error file=… annotation pointing at the offending manifest.
• CLAUDE.md — documents the convention under a new ## Modifying an Existing Plugin section.

Test plan

• CI green on this PR itself (no plugin files changed → workflow short-circuits with "No plugin files changed — nothing to check.")
• Open a follow-up PR that touches a skills/<name>/ file without bumping the manifest and confirm this workflow fails it

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@myasnikovdaniil has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 59 minutes and 48 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4c32532f-91bc-4306-8145-16d0e831c812

📥 Commits

Reviewing files that changed from the base of the PR and between d97a3d4 and 2408481.

📒 Files selected for processing (2)

• .github/workflows/check-plugin-version-bump.yml
• CLAUDE.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/check-plugin-version-bump

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request updates CLAUDE.md to document the requirement for version bumps when modifying existing plugins. The feedback highlights that the GitHub Actions workflow mentioned in the documentation is missing from the current changes. It is also suggested to clarify that this rule applies specifically to updates of existing plugins to avoid confusion for contributors adding new ones.

[IvanHunters]

Requesting changes — the workflow watches a repository layout that no longer exists, so it enforces nothing.

• This branch's base is a month behind main, from before the top-level agents/ hooks/ mcp/ skills/ layout was replaced by plugins/<vendor>/skills/<name>/. The workflow triggers on skills/** agents/** hooks/** mcp/**, but on current main those top-level dirs hold only .gitkeep — every real plugin now lives under plugins/. A change to any real plugin (exactly what #15 does to plugins/cozystack/skills/dev-ui-bootstrap/SKILL.md) will not trigger the workflow at all, so the stated goal isn't met. Please rebase onto current main and rework for the plugins/** layout.
• The manifest-path derivation (cut -d/ -f2 producing <category>/<name>/.claude-plugin/plugin.json) is also wrong for the new layout, where the manifest is at plugins/<vendor>/.claude-plugin/plugin.json (vendor level) while changed files are at plugins/<vendor>/skills/<name>/....

Non-blocking once rebased: deleting or renaming a whole plugin trips a false "missing .version on HEAD" (consider --diff-filter / -M); a malformed base manifest silently skips the bump check (only the HEAD side fails closed). The version_gt comparator itself is correct.

(For the record: the two "human" review points are author replies to the gemini bot; gemini's "workflow file not included" claim is a false positive — the file is present in the diff and on HEAD.)