release SKILL.md skillA
release from hyhmrright/brooks-lint is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hyhmrright/brooks-lint/release@git:20261024.672ec0fPins git:20261024.672ec0f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hyhmrright/brooks-lint
- Path
.agents/skills/release/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261024.672ec0f, committed Oct 24, 2026
- First version recorded
- Oct 16, 2026
- Size
- 5,816 bytes
- Repository stars
- 1,554
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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. 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 …
Read the whole file at its exact version.
How to install
mdr add hyhmrright/brooks-lint/release@sha256:05d08e5daa861085The line at the top of this page pins the label git:20261024.672ec0f, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_z7sb7ruo3byekrdt)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 16, 2026 and Oct 24, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.672ec0f latest | 2026-10-24 | 672ec0f | 5,816 B | A | view · diff |
| git:20261024.b87e7d8 | 2026-10-24 | b87e7d8 | 5,317 B | A | view · diff |
| git:20261016.05cd4ff | 2026-10-16 | 05cd4ff | 4,725 B | A | view · diff |
| git:20261016.c7fa1b0 | 2026-10-16 | c7fa1b0 | 4,664 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5816 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
hyhmrright/brooks-lint · 1,554 stars · license MIT · pushed 2026-10-26 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_z7sb7ruo3byekrdt GET https://markdownregistry.com/api/v1/resolve?ref=hyhmrright/brooks-lint/release GET https://markdownregistry.com/api/v1/blob/05d08e5daa861085a05bd43ef98ce91518d6bc4338f5790e2f579982c4749b34
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from hyhmrright/brooks-lint
Every file in hyhmrright/brooks-lint