ci: automate releases with release-please manifest mode (#51)

* ci: automate releases with release-please manifest mode

One release-please package per plugin (release-type simple); each package
syncs its version into .claude-plugin/marketplace.json via a root-relative
extra-files jsonpath filter. PR titles are linted as conventional commits
since squash-merge titles are what release-please reads. /version-plugin
no longer bumps versions by hand — it registers new plugins and points
updates at the conventional-commit flow.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* ci: enforce conventional commits locally; fold /version-plugin into CLAUDE.md

Mirror Scout's guardrails: husky commit-msg hook running commitlint
(config-conventional) via a tooling-only private package.json. The
version-plugin skill is removed — release-please owns version bumps and
the new-plugin registration checklist now lives in CLAUDE.md.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

Author: pcamarajr

.claude/skills/version-plugin/SKILL.md

@@ -0,0 +1,29 @@
+name: lint-pr-title
+
+on:
+  pull_request:
+    types: [opened, edited, synchronize, reopened]
+
+permissions:
+  pull-requests: read
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: amannn/action-semantic-pull-request@v6
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          # Squash-merge: the PR title becomes the commit on main that
+          # release-please reads — the scope should be the plugin name.
+          scopes: |
+            astro-builder
+            astro-lsp
+            content-image-gemini
+            content-ops
+            content-seo
+            cost-tracker
+            marketplace
+            deps
+          requireScope: false

.github/workflows/lint-pr-title.yml

@@ -0,0 +1,15 @@
+name: release-please
+
+on:
+  push:
+    branches: [main]
+
+permissions:
+  contents: write
+  pull-requests: write
+
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: googleapis/release-please-action@v5

.github/workflows/release-please.yml

@@ -1,3 +1,4 @@
+node_modules/
 .claude/worktrees/
 .claude/settings.local.json
 .worktrees/

.gitignore

@@ -0,0 +1 @@
+npx --no -- commitlint --edit "$1"

.husky/commit-msg

@@ -0,0 +1,8 @@
+{
+  "astro-builder": "1.8.0",
+  "astro-lsp": "1.0.1",
+  "content-image-gemini": "1.0.0",
+  "content-ops": "0.7.0",
+  "content-seo": "2.0.0",
+  "cost-tracker": "0.3.0"
+}

.release-please-manifest.json

@@ -37,12 +37,23 @@ Every plugin entry must have: `name`, `version` (semver), `description`, `author
 
 ---
 
+## Releases
+
+Versions are managed by **release-please** (manifest mode, one package per plugin) — never bump a `version` by hand. PRs are squash-merged, so the PR title must be a conventional commit scoped to the plugin (e.g. `feat(astro-builder): ...`); `feat`/`fix`/`!` trigger releases, `chore`/`docs`/`refactor`/`ci` do not — a refactor users will perceive as a feature should be titled `feat(...)`. Merging the release PR that release-please opens updates `marketplace.json` + the plugin's `CHANGELOG.md`/`version.txt` and cuts the tag (`<plugin>-v<version>`) and GitHub Release. Config: `release-please-config.json` + `.release-please-manifest.json`.
+
+Commit messages and PR titles/descriptions are always written in English. Conventional-commit format is enforced locally by a husky `commit-msg` hook (commitlint — run `npm install` once to activate) and in CI by the PR-title lint.
+
 ---
 
 ## Adding a new plugin
 
 1. Create the plugin directory with `README.md` and its components
-2. Run `/version-plugin` — it will register the entry in `marketplace.json` and update the root `README.md`
+2. Add the entry to `.claude-plugin/marketplace.json` with `version: "1.0.0"` — the only time a version is written by hand
+3. Scaffold `<plugin>/.claude-plugin/plugin.json` (name, description, author, repository, license — no `version` field; version lives exclusively in `marketplace.json`)
+4. Register in `release-please-config.json` (copy an existing `packages` entry, adjusting the plugin name in the key and the jsonpath) and `.release-please-manifest.json` (`"<plugin>": "1.0.0"`)
+5. Add the plugin name to the `scopes` list in `.github/workflows/lint-pr-title.yml`
+6. Add the plugin section to the root `README.md`, in alphabetical order
+7. Title the PR `feat(<plugin>): ...` — `feat` makes release-please cut the plugin's first release, anchored at `1.0.0` by the manifest
 
 ---
 

CLAUDE.md

@@ -0,0 +1 @@
+export default { extends: ["@commitlint/config-conventional"] };