release
Skill1.2k starsChanged 13 days agoMITView on GitHub
Prepare a release of the zxcvbn-ts packages: pick versions, update dependency ranges and write CHANGELOG.md entries from the diffs, left uncommitted for review. Use for "prepare a release", "prepare a beta release", "finish the beta", or `/release [beta|finish-beta]`.
193 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
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 zxcvbn-ts/zxcvbn
- antoantonyk/password-strength-meter“Use different zxcvbn fork”GitHub · May 4, 2021 · 6 reactions
- apertureless/vue-password-strength-meter“Use of the newest fork of zxcvbn”GitHub · May 24, 2021 · 3 reactions
- dropbox/zxcvbn“Different score for the password strength for the same string between TypeScript and Java versions”GitHub · May 10, 2022 · 2 reactions
- MrWook/zxcvbn“Point to actively maintained repo”GitHub · May 4, 2021 · 2 reactions
- Attraccess/Attraccess“build(deps): bump the npm-minor-patch group across 1 directory with 59 updates”GitHub · Sep 22, 2026 · 1 reactions
The biggest 5 of 50 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 50
Talked about on GitHub (50 times).
On GitHub · 50
- May 4, 2021Use different zxcvbn fork — antoantonyk/password-strength-meter6 reactions · 2 comments
- May 24, 2021Use of the newest fork of zxcvbn — apertureless/vue-password-strength-meter3 reactions
- May 10, 2022Different score for the password strength for the same string between TypeScript and Java versions — dropbox/zxcvbn2 reactions · 5 comments
- May 4, 2021Point to actively maintained repo — MrWook/zxcvbn2 reactions
- Sep 22, 2026build(deps): bump the npm-minor-patch group across 1 directory with 59 updates — Attraccess/Attraccess1 reaction · 6 comments
45 more on GitHub
- Sep 13, 2026build(deps): bump the npm-minor-patch group across 1 directory with 47 updates — Attraccess/Attraccess1 reaction · 4 comments
- Jun 20, 2021Switch to zxcvbn-ts — phpmyadmin/phpmyadmin1 reaction · 1 comment
- Feb 8, 2021Redesigned into Typescript — dropbox/zxcvbn1 reaction · 1 comment
- Nov 9, 2026chore(deps): Bump the production-minor-patch group with 21 updates — linhgrr/rinkuzu0 reactions · 2 comments
- Nov 9, 2026chore(deps): bump the bo-new-theme-npm group across 1 directory with 33 updates — gRoussac/GregoShop0 reactions
- Nov 9, 2026deps: bump @zxcvbn-ts/language-nl-be from 3.0.2 to 4.1.1 — forwardemail/forwardemail.net0 reactions
- Nov 9, 2026deps(deps): bump the production-dependencies group across 1 directory with 18 updates — SEP490-G29-TrekSphere/TrekSphere---CloneUI0 reactions · 1 comment
- Nov 2, 2026build(deps): bump @zxcvbn-ts/core from 4.1.2 to 4.2.0 — element-hq/matrix-authentication-service0 reactions · 1 comment
- Nov 1, 2026Bump @zxcvbn-ts/language-common from 4.1.2 to 4.1.3 in /materialious — Materialious/Materialious0 reactions · 1 comment
- Nov 1, 2026Bump @zxcvbn-ts/core from 4.1.2 to 4.2.0 in /materialious — Materialious/Materialious0 reactions · 1 comment
- Oct 25, 2026chore(deps): bump @zxcvbn-ts/language-common from 3.0.4 to 4.1.3 — sapientorius/nodePass0 reactions
- Oct 19, 2026STR-REUSE-TEXT — ADOTTA @zxcvbn-ts/core@4.2.0 per password-strength-estimator — domenicomassafra/Strumentini.it0 reactions · 1 comment
- Oct 19, 2026deps(deps): bump the production-dependencies group across 1 directory with 20 updates — SEP490-G29-TrekSphere/TrekSphere_FE0 reactions
- Oct 14, 2026build(deps): bump the zxcvbn group with 3 updates — Weavestream/Weavestream0 reactions · 3 comments
- Oct 10, 2026Bump @zxcvbn-ts/language-en from 3.0.2 to 4.1.1 — mksdr/Veli0 reactions · 1 comment
- Oct 10, 2026Bump @zxcvbn-ts/core from 3.0.4 to 4.2.0 — mksdr/Veli0 reactions · 1 comment
- Oct 10, 2026Bump @zxcvbn-ts/language-common from 3.0.4 to 4.1.3 — mksdr/Veli0 reactions · 1 comment
- Oct 1, 2026Bump @zxcvbn-ts/language-en from 3.0.2 to 4.1.1 — AlfredoRamos/csp-reporter-frontend0 reactions
- Oct 1, 2026Bump @zxcvbn-ts/matcher-pwned from 4.1.2 to 4.1.3 — AlfredoRamos/csp-reporter-frontend0 reactions
- Sep 29, 2026build(deps): bump @zxcvbn-ts/core from 4.1.2 to 4.2.0 — hafgit99/kalderashield0 reactions
- Sep 28, 2026chore(deps): Bump @zxcvbn-ts/core from 4.1.2 to 4.2.0 in /frontend — avgarcia/runcriticon0 reactions · 1 comment
- Sep 28, 2026chore(deps): bump @zxcvbn-ts/language-en from 3.0.2 to 4.1.1 — vbutiu/dev-tools0 reactions
- Sep 24, 2026migrate: @zxcvbn-ts/* 3 → 4 — tkarakai/web-app-starter0 reactions · 2 comments
- Sep 21, 2026deps: bump @zxcvbn-ts/language-it from 3.0.2 to 4.1.1 — forwardemail/forwardemail.net0 reactions · 1 comment
- Sep 19, 2026Bump @zxcvbn-ts/core from 4.1.2 to 4.2.0 in /apps/desktop — CyberDefenseNova/gestionnaire-de-mot-de-passe-CyberDefense-Nova0 reactions · 1 comment
- Sep 12, 2026Score of passphrase consisting of user input is too high — shssoichiro/zxcvbn-rs0 reactions
- Sep 10, 2026build(deps): bump the npm-minor group across 1 directory with 7 updates — ilionel/BenchPass0 reactions
- Sep 7, 2026chore(deps): bump the major-updates group across 1 directory with 12 updates — The-Orange-Way/Orange-Way-Books0 reactions · 8 comments
- Sep 1, 2026Bump @zxcvbn-ts/core from 4.1.2 to 4.2.0 in /frontend in the npm-minor-patch group — wybaby168/passguard0 reactions
- Aug 30, 2026chore(deps): bump the npm-major group across 1 directory with 8 updates — rapiip/cyberkit0 reactions
- Aug 9, 2026build(deps): bump @zxcvbn-ts/language-common from 3.0.4 to 4.1.3 — jadrianports/cryptiq0 reactions
- Jul 19, 2026build(deps): bump @zxcvbn-ts/core from 3.0.4 to 4.1.2 — jadrianports/cryptiq0 reactions
- Jul 19, 2026build(deps): bump @zxcvbn-ts/language-en from 3.0.2 to 4.1.1 — jadrianports/cryptiq0 reactions
- Jul 19, 2026chore(deps): bump the prod-dependencies group across 1 directory with 8 updates — Aquitano/aqt-ui0 reactions
- Jun 15, 2026chore(deps)(deps): Bump @zxcvbn-ts/core from 3.0.4 to 4.1.1 in the prod-dependencies group — antonyblain/sentinel-nudge0 reactions · 1 comment
- Jun 15, 2026chore(deps): bump @zxcvbn-ts/core from 3.0.4 to 4.1.1 — GilbertIrumva/scholarship-hub0 reactions · 1 comment
- Jun 14, 2026Bump @zxcvbn-ts/language-it from 3.0.2 to 4.1.0 — hedashuaibi/ct-couplecards-b35916700 reactions
- Jun 14, 2026Bump @zxcvbn-ts/language-de from 3.0.2 to 4.1.0 — hedashuaibi/ct-couplecards-b35916700 reactions
- Jun 14, 2026Bump @zxcvbn-ts/core from 3.0.4 to 4.1.1 — hedashuaibi/ct-couplecards-b35916700 reactions
- Jun 14, 2026Bump @zxcvbn-ts/language-es-es from 3.0.2 to 4.1.0 — hedashuaibi/ct-couplecards-b35916700 reactions
- Jun 14, 2026Bump @zxcvbn-ts/language-de from 3.0.2 to 4.1.0 in /server — hedashuaibi/ct-couplecards-b35916700 reactions
- Jun 14, 2026Bump @zxcvbn-ts/language-es-es from 3.0.2 to 4.1.0 in /server — hedashuaibi/ct-couplecards-b35916700 reactions
- Jun 14, 2026Bump @zxcvbn-ts/language-en from 3.0.2 to 4.1.0 — hedashuaibi/ct-couplecards-b35916700 reactions
- Jun 14, 2026Bump @zxcvbn-ts/language-it from 3.0.2 to 4.1.0 in /server — hedashuaibi/ct-couplecards-b35916700 reactions
- Jun 14, 2026Bump @zxcvbn-ts/language-en from 3.0.2 to 4.1.0 in /server — hedashuaibi/ct-couplecards-b35916700 reactions
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 versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- 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
183 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 repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
Only non-code changes to published files (README, NOTICE, licence): list the package and ask the maintainer.
- Distinctive: line 63
Only packages that changed, or need a range update, get a beta.
- Very specific: line 69
If it falls outside a dependent's range (a core major.
- Distinctive: line 70
If the dependent's own changes rely on something only in the new version, raise the range.
- Distinctive: line 81
every bullet links its PR and commit
- Distinctive: line 83
Leave out internal refactors, test-only changes, and anything introduced and fixed between the two releases: users never had that bug.
- Very specific: line 90
First run only: if packages/libraries/main/CHANGELOG-4.3.0.md exists, it is a reviewed draft of core's next entry.
“Common” is measured: kept by at least 6 in 10 of the 183 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
Prepare a release
Arguments: $ARGUMENTS. Empty means a stable release, beta a beta release, finish-beta moves the packages in an open beta series to stable.
This skill is the prepare half. It edits version fields, internal dependency ranges and CHANGELOG.md files, and nothing else. The maintainer reviews, commits, then runs yarn release, which builds, tags, pushes and publishes whatever is committed but not yet on origin or npm. Leave every change uncommitted: committing, tagging and publishing are the maintainer's.
Publishable packages: every non-private package.json under packages/libraries/* and packages/languages/*.
Steps
1. Find candidates
For each publishable package:
- Last release: its newest tag
<name>@<version>, found withgit -c versionsort.suffix=- tag --list '<name>@*' --sort=-v:refname | head -1. Use the tag, never thepackage.jsonversion, so a second run before publishing builds on its own uncommitted bumps instead of bumping twice. - Last stable release: its newest tag without a prerelease part.
- Open beta series: the newest tag is a prerelease (e.g.
5.0.0-beta.2). - Commits since:
git log <last release tag>..HEAD -- <package dir>.
Shared build inputs make every package a candidate: scripts/rollup.config.mjs, scripts/jsonPlugin.mjs, the root tsconfig.json, and root package.json dependencies that end up in bundles (@zxcvbn-ts/dictionary-compression's decompressor is bundled into every package with dictionaries; babel and rollup plugins change emitted code). Judge per package whether its built output actually changes.
Done when every publishable package has a last release, a last stable release and a commit list (possibly empty).
2. Read the changes
For every candidate commit, read the body, the diff of published files (src, package.json, README, NOTICE, licence) and the tests added with it. Squash-merged PRs bundle many changes behind one subject; the tests show the user-visible effect best. Look up the PR number from the subject (#123) when there is one.
Done when you can say, for each candidate package, every user-visible change and the commit and PR it came from.
3. Decide per package
- Changes that never reach users (tests only, repo tooling, unpublished files): skip, and list the package with the reason.
- Only non-code changes to published files (README, NOTICE, licence): list the package and ask the maintainer.
- Something a user of the package would notice: release.
- A dependency range that has to change (step 5): release.
4. Pick versions
Which kind each released package gets:
- In an open beta series, and the argument isn't
finish-beta: the next beta. finish-beta: packages in an open beta series go stable, at the series' target version (5.0.0-beta.3→5.0.0).- Otherwise stable, or with
betathe first beta of a new series.
One run can mix kinds; the handover table shows which is which and the maintainer can move a package between them.
Stable, from the last release:
- major: a breaking change to the public API or documented behaviour
- minor: a new feature, option or export
- patch: fixes and performance only
Changes that move scores (guesses, score, feedback) are called out in the changelog; they aren't breaking on their own.
Beta:
- The first beta is
<target>-beta.0. Propose the target (usually the next major) and get the maintainer's confirmation before writing anything. - Later betas increment the number:
5.0.0-beta.2→5.0.0-beta.3. - Only packages that changed, or need a range update, get a beta.
5. Update dependency ranges
The internal dependencies are in each package's dependencies (today only @zxcvbn-ts/matcher-pwned → @zxcvbn-ts/core). For each new version:
- If it falls outside a dependent's range (a core major; a core beta against
^4.2.0), update the range and release the dependent too. Its changelog entry says the range changed. - If the dependent's own changes rely on something only in the new version, raise the range.
- Otherwise leave the range alone. A release that only bumps a version has no place here.
6. Write the changelog entries
Prepend one entry per released package to its CHANGELOG.md, below the # Change Log header block, in the format in the next section, with today's date. Each entry is written for a user of the package:
- what changed for them, with a concrete example (a password, an option, a call) where it helps
- fixes that change scores, listed first among the bug fixes, overestimation fixes (passwords rated stronger than they are) before the rest; say which way scores move
- changes that only apply with an option name the option
- one bullet per change, even when one PR carries a dozen; one bullet with nested sub-bullets when several changes share a scope and a condition
- every bullet links its PR and commit
Leave out internal refactors, test-only changes, and anything introduced and fixed between the two releases: users never had that bug.
Scope of the entry:
- Stable: changes since the last release.
- Beta: changes since the previous beta; for
beta.0, since the last stable release. - Stable after a beta series: everything since the last stable release, compare link from the last stable tag. The beta entries stay below it as history.
First run only: if packages/libraries/main/CHANGELOG-4.3.0.md exists, it is a reviewed draft of core's next entry. Fold it into core's CHANGELOG.md, update it for anything merged since and for the version you picked, and delete the draft file.
Done when every released package has an entry, every user-visible change from step 2 appears in exactly one bullet, and every bullet has its links.
7. Hand over
Print:
- A table: package, old → new version, dist-tag (
latest, or the prerelease id such asbeta), kind (stable / beta), one-line reason. - Skipped packages, each with its reason.
- Open questions (first beta target, README-only packages, anything you weren't sure about).
- Next steps: review and edit the changes, commit them, run
yarn release.
Changelog format
The format conventional-changelog wrote so far; match the existing entries exactly.
# [4.3.0](https://github.com/zxcvbn-ts/zxcvbn/compare/@zxcvbn-ts/core@4.2.0...@zxcvbn-ts/core@4.3.0) (2026-11-03)
### Bug Fixes
- **scope:** what changed for the user ([#351](https://github.com/zxcvbn-ts/zxcvbn/issues/351)) ([cc45dd7](https://github.com/zxcvbn-ts/zxcvbn/commit/cc45dd7650e5232c0c324e98daf84a3a133d1e9c))
### Features
### Performance Improvements
### BREAKING CHANGES- Heading level:
#for major and minor releases,##for patch releases. A prerelease takes the level of its target (5.0.0-beta.1→#). - Compare link:
<previous tag>...<new tag>, previous tag being the one the entry's scope starts from (step 6). - Sections in this order, only those with bullets.
**scope:**is optional; use the matcher or area name (l33t,levenshtein,options).- Links: PR as
([#N](https://github.com/zxcvbn-ts/zxcvbn/issues/N)), commit as([abbrev7](https://github.com/zxcvbn-ts/zxcvbn/commit/<full sha>)). Several of either go comma-separated inside one pair of parentheses. Commits without a PR get only the commit link. - A short paragraph under a section heading is fine when it applies to all bullets (e.g. "most of these fixes lower the guesses for …").
- A range change:
- **deps:** requires @zxcvbn-ts/core ^5.0.0under Bug Fixes, or under BREAKING CHANGES when users must upgrade core with it.
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.

