release
Skill10 starsChanged 3 months agoMITView on GitHub
Release management for HoloScript monorepo. Handles changeset generation, version bumping, changelog generation, npm publish coordination across packages, and git tagging. Uses changesets and pnpm workspace conventions.
- Commits and pushes
196 other projects use a version of this.
Adopted by
Most recently taken up by
- zxcvbn-ts/zxcvbntheir own version, first seen Nov 9, 2026
- TechbeeAT/jtxBoardtheir own version, first seen Nov 9, 2026
- ddnexus/pagytheir own version, first seen Nov 9, 2026
- zerx-lab/FluxDowntheir own version, first seen Nov 9, 2026
- orioledb/orioledbtheir own version, first seen Nov 9, 2026
- AmruthPillai/Reactive-Resumetheir own version, first seen Nov 8, 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 versions196 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 196
- paperclipai/paperclip★ 112ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 72ksame name
- traefik/traefik★ 65ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 63ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- amruthpillai/reactive-resume★ 45ksame name
- reactive-resume/reactive-resume★ 45ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
186 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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/holodoor-security.mdcCursor rule
- .cursor/rules/team-peer-protocol.mdcCursor rule
- absorbSkill
- benchmarkSkill
- bio-discoverySkill
- devSkill
- frontendSkill
- holoscript-adminSkill
- holoscript-videoSkill
- marketplaceSkill
- migrateSkill
- neuroSkill
- simSkill
- toolsSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 186 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 80
Create and push a git tag for a release.
- Very specific: line 90
All tests passing (pnpm test)
- Distinctive: line 96
No hardcoded stats in docs or skills
- Distinctive: line 103
All other packages (parallel)
“Common” is measured: kept by at least 6 in 10 of the 186 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
/holoscript:release — Release Management
Command: $ARGUMENTS
Overview
Coordinate releases across the HoloScript monorepo. Handles the full lifecycle from changeset creation to npm publish.
Subcommands
status — Release Readiness Check
cd C:/Users/Josep/Documents/GitHub/HoloScript
echo "=== Pending Changesets ==="
ls .changeset/*.md 2>/dev/null | grep -v README || echo "None"
echo "=== Current Versions ==="
for pkg in packages/*/package.json; do
name=$(python3 -c "import json; print(json.load(open('$pkg'))['name'])")
ver=$(python3 -c "import json; print(json.load(open('$pkg'))['version'])")
echo " $name@$ver"
done
echo "=== Unpublished Commits ==="
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~10)..HEAD --no-merges | head -20
echo "=== Test Status ==="
pnpm test -- --run 2>&1 | tail -5changeset — Create a Changeset
Interactive changeset creation for the current work.
cd C:/Users/Josep/Documents/GitHub/HoloScript
pnpm changesetversion — Bump Versions
Apply pending changesets to bump package versions and update changelogs.
cd C:/Users/Josep/Documents/GitHub/HoloScript
pnpm changeset versionpublish — Publish to npm
Publish all changed packages to the npm registry.
cd C:/Users/Josep/Documents/GitHub/HoloScript
# Verify build first
pnpm build
# Dry run
pnpm changeset publish --dry-run
# Actual publish (requires confirmation)
echo "Ready to publish. Awaiting confirmation..."tag <version> — Git Tag
Create and push a git tag for a release.
cd C:/Users/Josep/Documents/GitHub/HoloScript
git tag -a "v$1" -m "Release v$1"
echo "Tag v$1 created. Push with: git push origin v$1"Release Checklist
- All tests passing (
pnpm test) - Build succeeds (
pnpm build) - Changesets describe all user-facing changes
- CHANGELOG.md entries are clear and accurate
- Version bumps follow semver (breaking = major, feature = minor, fix = patch)
docs/NUMBERS.mdverification commands still work- No hardcoded stats in docs or skills
Package Publishing Order
Core must publish first due to workspace dependencies:
@holoscript/core@holoscript/engine- All other packages (parallel)
@holoscript/mcp-server(last — depends on everything)
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.

