release
Skill1.6k starsChanged 24 days agoMITView on GitHub
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.
- Commits and pushes
194 other projects use a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- vulnerability-lookup/vulnerability-lookuptheir own version, first seen Nov 16, 2026
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 2026
Who's talking about hyhmrright/brooks-lint
- A Hacker News story“Show HN: Brooks-Lint – AI code reviews grounded in 12 classic engineering books”Hacker News · Jun 11, 2026 · 8 points
- hashgraph-online/awesome-codex-plugins“Add brooks-lint — AI code reviews from classic engineering books”GitHub · Apr 1, 2026 · 3 reactions
- sudosubin/agents.nix“claude-code-marketplaces.github.hyhmrright.brooks-lint: init at 1.9.1”GitHub · Oct 28, 2026
- sbalswa/oculix“Add CONTRIBUTING.md”GitHub · Oct 26, 2026
- sudosubin/agents.nix“claude-code-plugins.github.hyhmrright.brooks-lint: 1.8.0 → 1.9.1”GitHub · Oct 24, 2026
The biggest 5 of 31 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 31
Talked about on GitHub and Hacker News (31 times).
On GitHub · 30
- Apr 1, 2026Add brooks-lint — AI code reviews from classic engineering books — hashgraph-online/awesome-codex-plugins3 reactions · 6 comments
- Oct 28, 2026claude-code-marketplaces.github.hyhmrright.brooks-lint: init at 1.9.1 — sudosubin/agents.nix0 reactions
- Oct 26, 2026Add CONTRIBUTING.md — sbalswa/oculix0 reactions
- Oct 24, 2026claude-code-plugins.github.hyhmrright.brooks-lint: 1.8.0 → 1.9.1 — sudosubin/agents.nix0 reactions
- Oct 24, 2026agent-skills.github.hyhmrright.brooks-lint: 1.8.0 → 1.9.1 — sudosubin/agents.nix0 reactions
25 more on GitHub
- Oct 24, 2026[plugin-add] brooks-lint — polang233/dsh-plugin-index0 reactions · 1 comment
- Oct 24, 2026Add brooks-lint code quality skills — awesome-dsh-plugin/awesome-dsh-plugin0 reactions
- Oct 16, 2026claude-code-plugins.github.hyhmrright.brooks-lint: 1.7.0 → 1.8.0 — sudosubin/agents.nix0 reactions
- Oct 16, 2026agent-skills.github.hyhmrright.brooks-lint: 1.7.0 → 1.8.0 — sudosubin/agents.nix0 reactions
- Oct 4, 2026[Candidate] hyhmrright/brooks-lint/.claude/skills/release - release — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 4, 2026[Candidate] hyhmrright/brooks-lint/.claude/skills/new-skill - new-skill — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 4, 2026[Candidate] hyhmrright/brooks-lint/.claude/skills/brooks-harness - brooks-harness — ProSkillsMD/proskills0 reactions · 1 comment
- Oct 4, 2026claude-code-plugins.github.hyhmrright.brooks-lint: init at 1.7.0 — sudosubin/agents.nix0 reactions
- Sep 28, 2026agent-skills.github.hyhmrright.brooks-lint: init at 1.7.0 — sudosubin/agents.nix0 reactions
- Sep 27, 2026[gap] Curated knowledge-grounded rule packs — sblattj/prxref0 reactions
- Sep 27, 2026[gap] Review-score trending with regression gate — sblattj/prxref0 reactions
- Sep 14, 2026Weekly discovery: new DeepSeek Harness ecosystem candidates — fendouai/awesome-deepseek-harness0 reactions · 1 comment
- Aug 17, 2026Weekly discovery: new DeepSeek Harness ecosystem candidates — fendouai/awesome-deepseek-harness0 reactions · 1 comment
- Apr 29, 2026feat: add brooks-lint and logic-lens skills for AI-powered code review — anthropics/skills0 reactions
- Apr 29, 2026Feature Request: Add brooks-lint skill — AI code reviewer grounded in 12 classic engineering books — affaan-m/ECC0 reactions · 1 comment
- Apr 22, 2026[Resource]: brooks-lint — hesreallyhim/awesome-claude-code0 reactions · 1 comment
- Apr 2, 2026[Resource]: brooks-lint — hesreallyhim/awesome-claude-code0 reactions · 1 comment
- Mar 31, 2026Add brooks-lint — book-backed AI code review skill — ComposioHQ/awesome-claude-skills0 reactions
- Mar 31, 2026Add brooks-lint — book-backed AI code review plugin — rohitg00/awesome-claude-code-toolkit0 reactions · 1 comment
- Mar 31, 2026Add brooks-lint — book-backed AI code review skill — travisvn/awesome-claude-skills0 reactions · 1 comment
- Mar 31, 2026Add brooks-lint — book-backed AI code review plugin — composio-community/awesome-claude-plugins0 reactions
- Mar 31, 2026Add brooks-lint extension — Piebald-AI/awesome-gemini-cli0 reactions
- Mar 31, 2026Add brooks-lint extension — Piebald-AI/awesome-gemini-cli-extensions0 reactions
- Mar 30, 2026[Community] brooks-lint: Claude Code plugin for book-backed code reviews (6 classic SE books) — anthropics/claude-code0 reactions · 2 comments
- Mar 27, 2026[Resource]: brooks-lint — hesreallyhim/awesome-claude-code0 reactions · 1 comment
On Hacker News · 1
- Jun 11, 2026Show HN: Brooks-Lint – AI code reviews grounded in 12 classic engineering books8 points · 1 comment
Used with
Projects with it also use create-agent-adapter, changelog-style and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
MicrosoftSkillcreate-agent-adapter
Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.
Also in 5 projects that use this
GrinvSkillchangelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.
Also in 4 projects that use this
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
GrinvSkilldocs-consistency-check
Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.
Also in 4 projects that use this
Microsoft AzureSkilldocumentation-consistency
Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.
Also in 8 projects that use this
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- +3 more from Grinv
Other versions194 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 194
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
184 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brooks-harnessSkill
- new-skillSkill
- brooks-harnessSkill
- new-skillSkill
- releaseSkill
- brooks-auditSkill
- brooks-debtSkill
- brooks-healthSkill
- brooks-reviewSkill
- brooks-sweepSkill
- brooks-testSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 184 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Before accepting that version, read the backlog: Run npm run changelog:audit and look at what is actually unreleased — the bump is decided …
- Very specific: line 42
Write the changelog: Add a new section at the top of CHANGELOG.md with categorized notes (Added / Fixed / Changed) summarizing the commits …
- Distinctive: line 91
If CI fails, diagnose and commit the fix, then wait for the new commit's CI.
- Very specific: line 92
Tag & publish: Only after the remote gate passes, create the GitHub release: gh release create v<version> --title "v<version>" --notes …
“Common” is measured: kept by at least 6 in 10 of the 184 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
brooks-lint — Release
Target version comes from the user request (e.g. 1.4.0). If empty, ask the maintainer
for the semver bump before doing anything.
Before accepting that version, read the backlog. Run
npm run changelog:audit and look at what is actually unreleased — the bump is decided by the whole range, not by the change
that prompted the release. If the range contains a feature or a new platform and
the maintainer asked for a patch, stop and say so: v1.5.1 was published, then
deleted and re-cut as v1.6.0 because twenty unreleased commits (including a new
platform) had been swept into a patch.
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-versionflag is required — plainnpm versionwould 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 byscripts/version-refs.mjs(all six README badges and actionuses:pins, the JSON-LDsoftwareVersionon the docs landing page, anddocs/github-action-example.yml). Do not maintain a list here — the script's is authoritative. Write the changelog. Add a new section at the top of
CHANGELOG.mdwith categorized notes (Added / Fixed / Changed) summarizing the commits since the last release tag. The heading MUST be## [<version>] - YYYY-MM-DD—npm run validateparses that exact shape and fails on a bare## <version>. 3a. Audit the range — every commit, no sampling. Run:npm run changelog:auditIt derives the range from the last release tag, applies the only three exemptions (the release bump, a merge commit whose branch commits are listed separately, and the star-history refresh — a bot commit touching only the chart's own two files) and prints the rest as a checklist. Walk it: each line gets an entry you just wrote, or a reason it needs none. Nothing else is exempt — internal hardening with no user-visible change earns an entry, and so does an outside contributor's maintainer-facing fix, which also earns an
@handlecredit. AChangelog:trailer on a commit is surfaced as a flag; that commit's entry is the one you are writing now.The script exits non-zero on the gap it can prove — a pull request in the range whose
#Nthe section never cites. That same check runs insidenpm run validatewhile a release is in progress, so it cannot be skipped, and validate prints one line whenever it stands down. The rest of the checklist is judgment and is not enforced. A green audit is not proof of a complete changelog: a bare#Nanywhere in the section clears the gate, a rebase-merged PR leaves nothing to match, and anything staged into the release bump itself is never audited. See AGENTS.md's Release Process.- 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. Thennpm test. - Commit & push. Stage everything
npm run bumprewrote plusCHANGELOG.md— readgit statusrather 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 tomain(direct-to-main repo — no PR). 5a. Synchronize release surfaces and approval. Check all six README translations, CHANGELOG, plugin manifests, website and installation guides against the release state. Runnpm run github:metadata -- --applyand then--checkto synchronize About, homepage, topics, and managed labels. Preserve unrelated labels. Honor explicit publication holds; completed preparation and green CI are not approval. Withdrawn npm versions cannot be reused, even when GitHub tags are deleted. 5b. Wait for remote CI on the exact release commit. After pushing, resolvegit rev-parse HEAD, find theValidateworkflow run whoseheadShamatches that commit, and wait for it withgh run watch <run-id> --exit-status. Inspect every matrix job. A missing, queued, cancelled, or failed run is not a pass. Local checks do not replace this gate. Do not create the GitHub release or publish to npm until this exact-commit run has completed successfully. If CI fails, diagnose and commit the fix, then wait for the new commit's CI. - Tag & publish. Only after the remote gate passes, 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

