release
Skill2 starsChanged 8 months agoApache-2.0View on GitHub
Full release process: version bump, changelog, quality checks, PR, CI monitoring, and changelog discussion covering both vibe-guard and vibe-guard-cloud.
- Installs packages
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- CoreBunch/Instatictheir own version, first seen Nov 16, 2026
- coredevices/PebbleOStheir own version, first seen Nov 16, 2026
- 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
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
- 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 repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- new-adapterSkill
- new-presetSkill
- new-ruleSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
19 rules. 0 are common, 14 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Read the current version:
- Distinctive: line 24
Check the latest published version:
- Very specific: line 37
Only fix:, chore:, docs:, etc.
- Very specific: line 47
Read the current CHANGELOG.md
- Distinctive: line 58
Follow the existing format in the file (Keep a Changelog specification)
- Distinctive: line 62
Run each check sequentially.
- Distinctive: line 72
If you fix code to pass checks, include those fixes in the commit.
- Distinctive: line 85
Never modify master directly
- Very specific: line 86
All operations on dev branch only
- Very specific: line 118
Read the failed check logs: gh run view <RUN_ID> --log-failed
- Distinctive: line 121
Wait for checks again
- Distinctive: line 123
Maximum 2 retry cycles: If checks still fail after 2 retries, stop and ask the user for guidance.
- Distinctive: line 129
Wait for user confirmation that the PR is merged and npm publish succeeded.
- Very specific: line 145
Check vibe-guard-cloud for recent changes:
- Distinctive: line 205
After each release, check whether the cloud documentation needs updates:
- Distinctive: line 216
All categories are listed
- Distinctive: line 217
No missing rule category pages
- Distinctive: line 226
If a category exists in source but has no matching doc page, create one following the format of existing pages.
- Distinctive: line 246
If any step fails unexpectedly, report the error and ask for guidance
“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
VGuard Release Process
Automate the full release lifecycle for VGuard. This skill replaces the manual release and publish-changelog commands.
Prerequisites
- Working directory is
C:/Development/vibe-guard - On the
devbranch with a clean working tree (or changes ready to include) - GitHub CLI (
gh) authenticated - npm registry accessible
Step 1: Determine Version Bump
- Read the current version:
node -p "require('./package.json').version" - Check the latest published version:
npm view @anthril/vguard version - Review commits since last tag:
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~20")..HEAD - Auto-detect bump type from conventional commits:
- Any commit with
BREAKING CHANGEfooter or!suffix → major - Any
feat:orfeat(…):commit → minor - Only
fix:,chore:,docs:, etc. → patch
- Any commit with
- Ask the user to confirm or override the version bump before proceeding.
Step 2: Update package.json
Edit the "version" field in package.json to the new version.
Step 3: Update CHANGELOG.md
- Read the current
CHANGELOG.md - Under
## [Unreleased], insert a new section:## [X.Y.Z] - YYYY-MM-DD - Group commits by type:
- Added —
feat:commits - Changed —
refactor:,chore:commits - Fixed —
fix:commits - Removed — anything that removes functionality
- Added —
- Clear the
## [Unreleased]section content (keep the heading) - Follow the existing format in the file (Keep a Changelog specification)
Step 4: Run Quality Checks
Run each check sequentially. If any fail, read the error output, fix the issue, and re-run. Maximum 3 attempts per check before stopping.
npm run lint
npm run format -- --check
npm run type-check
npm test
npm run buildIf you fix code to pass checks, include those fixes in the commit.
Step 5: Stage, Commit, Push
git add package.json CHANGELOG.md
# Also add any files fixed in Step 4
git commit -m "chore(release): bump version to X.Y.Z"
git push origin devSafety rules:
- Never force-push
- Never modify master directly
- All operations on
devbranch only
Step 6: Create PR
gh pr create --base master --head dev \
--title "chore(release): vX.Y.Z" \
--body "$(cat <<'EOF'
## Release vX.Y.Z
### Changes
<paste changelog excerpt here>
### Checklist
- [ ] Version bumped in package.json
- [ ] CHANGELOG.md updated
- [ ] All checks passing
EOF
)"Report the PR URL to the user.
Step 7: Monitor CI
gh pr checks <PR_NUMBER> --watchIf checks fail:
- Read the failed check logs:
gh run view <RUN_ID> --log-failed - Fix the issue
- Push the fix to
dev - Wait for checks again
Maximum 2 retry cycles. If checks still fail after 2 retries, stop and ask the user for guidance.
Step 8: Publish Changelog Discussion (Post-Merge)
This step runs AFTER the user confirms the PR has been merged and the publish workflow has completed.
- Wait for user confirmation that the PR is merged and npm publish succeeded.
- Get the version and tag:
VERSION=$(node -p "require('./package.json').version") TAG="v$VERSION" - Extract changelog content for this version from
CHANGELOG.md(the section between## [X.Y.Z]and the next## [). - Get commits since previous tag:
PREV_TAG=$(git describe --tags --abbrev=0 HEAD~1 2>/dev/null || echo "") git log --oneline "$PREV_TAG"..HEAD - Check vibe-guard-cloud for recent changes:
cd C:/Development/vibe-guard-cloud git log --oneline --since="2 weeks ago" --no-merges cd C:/Development/vibe-guard Build the discussion body covering BOTH repos:
# VGuard vX.Y.Z **Released:** YYYY-MM-DD **Install:** `npm install @anthril/vguard@X.Y.Z` ## What's Changed <changelog content from CHANGELOG.md> ## Cloud Updates <summary of vibe-guard-cloud changes, or "No cloud changes in this release." if none> ## Commits<commit list> ```Full changelog: https://github.com/anthril/vibe-guard/blob/master/CHANGELOG.md npm: https://www.npmjs.com/package/@anthril/vguard/v/X.Y.Z Release: https://github.com/anthril/vibe-guard/releases/tag/vX.Y.Z
- Get repository and changelog category IDs:
gh api graphql -f query='{ repository(owner: "anthril", name: "vibe-guard") { id, discussionCategories(first: 20) { nodes { id, name } } } }' - Create the discussion:
gh api graphql -f query=' mutation { createDiscussion(input: { repositoryId: "<REPO_ID>", categoryId: "<CHANGELOG_CATEGORY_ID>", title: "vX.Y.Z — <one-line summary>", body: "<formatted body>" }) { discussion { url } } } ' - Report the discussion URL to the user.
Step 9: Audit vibe-guard-cloud Documentation
After each release, check whether the cloud documentation needs updates:
- Compare rule counts — Get the total rule count and categories from vibe-guard source:
cd C:/Development/vibe-guard ls src/rules/*/index.ts | wc -l # Count categories grep -r "registerRule" src/rules/ | wc -l # Count rules - Check docs overview — Read
C:/Development/vibe-guard-cloud/src/content/docs/rules/overview.mdand verify:- Total rule count matches actual count
- All categories are listed
- No missing rule category pages
- Check for missing doc pages — Compare rule category directories against doc files:
If a category exists in source but has no matching doc page, create one following the format of existing pages.# Rule categories in source ls C:/Development/vibe-guard/src/rules/ # Doc pages that exist ls C:/Development/vibe-guard-cloud/src/content/docs/rules/ - Check sidebar navigation — Verify
C:/Development/vibe-guard-cloud/src/app/(public)/docs/layout.tsxlists all rule category pages in theNAV_ORDERRules section. - Check CLI reference — If new CLI commands were added, verify
C:/Development/vibe-guard-cloud/src/components/dashboard/CLIReferenceDialog.tsxincludes them. - Commit and push any docs updates to vibe-guard-cloud:
cd C:/Development/vibe-guard-cloud git add src/content/docs/ src/app/ src/components/ git commit -m "docs: update for vX.Y.Z release" git push origin master
Error Handling
- Never force-push or modify master directly
- All git operations on dev branch only
- Stop and ask the user after 2 CI failure retries
- Confirm version bump with user before proceeding
- If any step fails unexpectedly, report the error and ask for guidance
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.

