release
Skill9 starsChanged 8 months agoMITView on GitHub
This skill should be used when the user asks to "release a new version", "bump version", "create release tag", "update release notes", "prepare release", or performs any release-related operation for the simulink-automation-suite plugin.
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- yicheng47/runnertheir own version, first seen Nov 13, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 2026
- cubeplexai/cubeplextheir own version, first seen Nov 10, 2026
- bex-co/bextheir own version, first seen Nov 10, 2026
- Yeachan-Heo/oh-my-claudecodetheir own version, first seen Nov 9, 2026
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
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 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
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
rivet-devSkilllaunch-graphics
Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.
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
- reactive-resume/reactive-resume★ 46ksame name
- AmruthPillai/Reactive-Resume★ 45ksame 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 repository2 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- live-testSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 8 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Default release path is tag-driven GitHub auto release via .github/workflows/release.yml.
- Distinctive: line 23
Update manifests and schema:
- Very specific: line 40
Check report's Test Commit vs current HEAD
- Very specific: line 41
If close match: copy to docs/reports/archive/live-test-vX.Y.Z.md
- Distinctive: line 42
If large gap: warn "Live test report may be stale" — user decides
- Distinctive: line 44
If no report exists: warn "No live test report.
- Distinctive: line 47
Create and push annotated tag:
- Distinctive: line 86
Do not leave shipped behavior changes on an old version with a plan to "bump later".
- Very specific: line 98
Curated: use docs/release/ document whose filename matches vX.Y.Z
- Very specific: line 112
Default to a bilingual body in one top-level curated file docs/release/<date>-vX.Y.Z.md:
- Very specific: line 118
If too long: keep single top-level file with shorter Chinese summary, link to detailed companion at docs/release/zh-CN/<date>-vX.Y.Z.md.
- Very specific: line 120
Do not add a second top-level version-matching file — build_release_notes.py treats multiple matches as an error.
- Distinctive: line 129
Run from the branch containing the fix.
- Distinctive: line 146
Before releasing, verify all affected artifacts are updated:
- Distinctive: line 158
Before finishing release-related work:
“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
Release
Default release path is tag-driven GitHub auto release via .github/workflows/release.yml.
Files to Check First
.claude-plugin/plugin.json.claude-plugin/marketplace.jsonsimulink_cli/core.py—build_schema_payload()["version"]docs/release/scripts/check_release_metadata.pyscripts/build_release_notes.py.github/workflows/release.yml
Release Flow
- Pick version
X.Y.Z - Update manifests and schema:
.claude-plugin/plugin.json→version: "X.Y.Z".claude-plugin/marketplace.json→plugins[0].version: "X.Y.Z"simulink_cli/core.py→build_schema_payload()["version"]to"X.Y"(only when major.minor changes)docs/release/<date>-vX.Y.Z.mdwhen required (see Release Notes section)
- Validate locally:
python scripts/check_release_metadata.py --tag vX.Y.Z
python -m unittest tests.test_plugin_manifest_contract tests.test_marketplace_manifest_contract -v
python -m unittest discover -s tests -p "test_*.py" -v
claude plugin validate .
python scripts/build_release_notes.py --tag vX.Y.Z --ref HEAD- Archive live test report (if available):
- If
docs/reports/LIVE-TEST-REPORT.mdexists:- Check report's
Test Commitvs current HEAD - If close match: copy to
docs/reports/archive/live-test-vX.Y.Z.md - If large gap: warn "Live test report may be stale" — user decides
- Reference archived report in release notes Validation section
- Check report's
- If no report exists: warn "No live test report. Consider running /live-test first." — do not block release
- If
- Commit release changes
- Create and push annotated tag:
git tag -a vX.Y.Z -m "Release vX.Y.Z"
git push origin <branch>
git push origin vX.Y.Z.github/workflows/release.ymlcreates the GitHub Release automatically
Version Sync Rules
For release version X.Y.Z, all four must match:
| Location | Required Value |
.claude-plugin/plugin.json → version | X.Y.Z |
.claude-plugin/marketplace.json → plugins[0].version | X.Y.Z |
simulink_cli/core.py → build_schema_payload()["version"] | X.Y |
| Git tag | vX.Y.Z |
scripts/check_release_metadata.py enforces this. Any divergence fails validation.
When To Bump Version
Bump when the change is intended for a distributable release or changes shipped contract behavior.
Requires bump:
.claude-plugin/**skills/**README*simulink_cli/**- tests/docs that define shipped contract behavior
Does not require bump by itself:
.github/workflows/**.claude/rules/**,.claude/skills/**- internal planning/docs not shipped with the plugin
Do not leave shipped behavior changes on an old version with a plan to "bump later".
CLI Changes and Schema Version
simulink_cli/core.py is both the runtime schema source and a release metadata input. When CLI contract changes require a new release version, update schema version with the plugin major.minor rule (e.g., plugin 2.3.4 → schema "2.3").
Release Notes
Source Priority
scripts/build_release_notes.py writes the GitHub Release body:
- Curated: use
docs/release/document whose filename matchesvX.Y.Z - Fallback: generate deterministic notes from git history (no external AI, commit range from highest earlier semver tag, required sections: Summary, Highlights, Compatibility / Upgrade Notes, Validation)
When Curated Notes Are Required
- Major or minor release
- Patch that changes user-facing behavior in more than one notable way
- Upgrade or compatibility guidance needed
- Behavior that should be summarized more clearly than raw commit subjects
Optional only for trivial metadata-only or emergency republish cases.
Bilingual Strategy
Default to a bilingual body in one top-level curated file docs/release/<date>-vX.Y.Z.md:
- Full English release notes first
- Chinese section (
## 中文说明) for user-facing summary, highlights, and compatibility guidance - Validation may stay English-only
If too long: keep single top-level file with shorter Chinese summary, link to detailed companion at docs/release/zh-CN/<date>-vX.Y.Z.md.
Do not add a second top-level version-matching file — build_release_notes.py treats multiple matches as an error.
workflow_dispatch
Use only when:
- The tag already exists
- The original release job failed or was skipped
- The GitHub Release body must be regenerated after fixing docs or scripts
Run from the branch containing the fix. Do not use as the normal first-publish path.
CI Validation Order
The release workflow runs in this order:
scripts/check_release_metadata.py --tag vX.Y.Zpython -m unittest discover -s tests -p "test_*.py" -vclaude plugin validate .(when available on runner)- Fallback validation when
claudeunavailable:python -m unittest tests.test_plugin_manifest_contract tests.test_marketplace_manifest_contract -vpython scripts/check_release_metadata.py --tag vX.Y.Z
scripts/build_release_notes.pygh release createorgh release edit
Change Synchronization
Before releasing, verify all affected artifacts are updated:
CLI actions/arguments → update simulink_cli/core.py + simulink_cli/actions/*.py + tests + README.md, README.zh-CN.md, SKILL.md, reference.md
Error codes → reuse existing codes; update simulink_cli/core.py + docs + test_error_contract, test_runtime_error_mapping, test_docs_contract
Output budgets → keep scan→max_blocks,fields, inspect→max_params,fields, connections→max_edges,fields, find→max_results,fields semantics stable; update output-control tests
Release metadata → version-sync per Version Sync Rules above
Agent Checklist
Before finishing release-related work:
- Tag format is
vX.Y.Z - Manifest versions match (plugin.json, marketplace.json)
- Schema version matches plugin major.minor
- Release notes source is understood (curated vs fallback)
- Local validation passed
- No stale docs describing manual-only release flow
- Live test report reviewed (if available) — no unresolved FAIL items
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.

