skill-hyhmrright-brooks-lint-release · by Install
$ agentstack add skill-hyhmrright-brooks-lint-release ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-hyhmrright-brooks-lint-release) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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 manifests + badge.
- Set the source of truth.
npm 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.mdwith
categorized notes (Added / Fixed / Changed) summarizing the commits since the last release tag (git log ..HEAD --oneline). The heading MUST be ## [] - YYYY-MM-DD — npm run validate parses that exact shape and fails on a bare ## .
- Validate.
npm run validate— fails if any manifest, the README badge, or
the CHANGELOG entry is out of sync. Fix and re-run until clean. Then npm test.
- Commit & push. Stage the changed manifests, README, and CHANGELOG; commit
with a conventional message (chore(release): bump version to ); push to main (direct-to-main repo — no PR).
- Tag & publish. Create the GitHub release:
gh release create v --title "v" --notes "".
Report the released version and the GitHub release URL when done.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hyhmrright
- Source: hyhmrright/brooks-lint
- License: MIT
- Homepage: https://hyhmrright.github.io/brooks-lint/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.