How do I install the Release skill?

Run npx skillmds@latest add gabrielmoreira/release-7 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Release safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Release?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Release by gabrielmoreira — Agent Skill

Name: Release
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Release

Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release", "cut a release", "ship a new version", or "bump and publish" brooks-lint. Do NOT trigger for: propagating an already-decided version without releasing (use `npm run bump` directly), CHANGELOG edits alone, or questions about the release process that don't ask to perform it.

gabrielmoreira Updated Sep 21, 2026 17 repo stars

File contents

brooks-lint — Release

Target version comes from $ARGUMENTS (e.g. 1.4.0). If empty, ask the maintainer for the semver bump before doing anything.

Execute these steps in order. bump-version.mjs reads the version FROM package.json and does NOT touch the changelog — so the version edit and the CHANGELOG entry are manual; the script only fans the version out to the manifests and every version-bearing text file.

Set the source of truth. npm version <version> --no-git-tag-version (the --no-git-tag-version flag is required — plain npm version would create its own commit + tag and collide with the manual commit in step 5).
Propagate. npm run bump — writes the version into .claude-plugin/plugin.json, .claude-plugin/marketplace.json, .codex-plugin/plugin.json, gemini-extension.json, and every version-bearing text file discovered by scripts/version-refs.mjs (all six README badges plus the JSON-LD softwareVersion on the docs landing page). Do not maintain a list here — the script's is authoritative.
Write the changelog. Add a new section at the top of CHANGELOG.md with categorized notes (Added / Fixed / Changed) summarizing the commits since the last release tag (git log <last-tag>..HEAD --oneline). The heading MUST be ## [<version>] - YYYY-MM-DD — npm run validate parses that exact shape and fails on a bare ## <version>.
Validate. npm run validate — fails if any manifest, any version-bearing text file, or the CHANGELOG entry is out of sync. Fix and re-run until clean. Then npm test.
Commit & push. Stage everything npm run bump rewrote plus CHANGELOG.md — read git status rather than naming files, because the version-bearing set is discovered from disk and is more than one README; commit with a conventional message (chore(release): bump version to <version>); push to main (direct-to-main repo — no PR).
Tag & publish. Create the GitHub release: gh release create v<version> --title "v<version>" --notes "<changelog section>".

Report the released version and the GitHub release URL when done.

---name: release-7description: Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release", "cut a release", "ship a new version", or "bump and publish" brooks-lint. Do NOT trigger for: propagating an already-decided version without releasing (use `npm run bump` directly), CHANGELOG edits alone, or questions about the release process that don't ask to perform it.---# brooks-lint — ReleaseTarget version comes from `$ARGUMENTS` (e.g. `1.4.0`). If empty, ask the maintainerfor the semver bump before doing anything.Execute these steps in order. `bump-version.mjs` reads the version FROM`package.json` and does NOT touch the changelog — so the version edit and theCHANGELOG entry are manual; the script only fans the version out to the manifestsand every version-bearing text file.1. **Set the source of truth.** `npm version <version> --no-git-tag-version` (the `--no-git-tag-version` flag is required — plain `npm version` would create its own commit + tag and collide with the manual commit in step 5).2. **Propagate.** `npm run bump` — writes the version into `.claude-plugin/plugin.json`, `.claude-plugin/marketplace.json`, `.codex-plugin/plugin.json`, `gemini-extension.json`, and every version-bearing text file discovered by `scripts/version-refs.mjs` (all six README badges plus the JSON-LD `softwareVersion` on the docs landing page). Do not maintain a list here — the script's is authoritative.3. **Write the changelog.** Add a new section at the top of `CHANGELOG.md` with categorized notes (Added / Fixed / Changed) summarizing the commits since the last release tag (`git log <last-tag>..HEAD --oneline`). The heading MUST be `## [<version>] - YYYY-MM-DD` — `npm run validate` parses that exact shape and fails on a bare `## <version>`.4. **Validate.** `npm run validate` — fails if any manifest, any version-bearing text file, or the CHANGELOG entry is out of sync. Fix and re-run until clean. Then `npm test`.5. **Commit & push.** Stage everything `npm run bump` rewrote plus `CHANGELOG.md` — read `git status` rather than naming files, because the version-bearing set is discovered from disk and is more than one README; commit with a conventional message (`chore(release): bump version to <version>`); push to `main` (direct-to-main repo — no PR).6. **Tag & publish.** Create the GitHub release: `gh release create v<version> --title "v<version>" --notes "<changelog section>"`.Report the released version and the GitHub release URL when done.

Frequently asked questions