release
Skill54 starsChanged 2 months agoApache-2.0View on GitHub
Prepare and publish Perigon.CLI patch releases, including versioning, release notes, bilingual docs, validation, and the nuget-branch CI handoff.
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
- GrinvSkill
docs-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 AzureSkill
documentation-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.
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 2 are distinctive, and 9 are very specific to this project.
0
Common
Most of the 186 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 8
Use this skill when releasing Perigon.CLI or when the user asks to package and publish a version.
- Very specific: line 19
Keep src/Apps/Dashboard/Dashboard.csproj on the same version.
- Very specific: line 20
Update <PackageReleaseNotes> with only the changes being released.
- Very specific: line 21
Update the matching Chinese and English pages under Perigon.docs/Content/docs/Perigon, normally the command-line page and the version …
- Very specific: line 22
Add or update reusable release guidance in this skill and Contribution.md when the workflow changes.
- Distinctive: line 26
Run the focused tests for the changed feature, then the full test project:
- Distinctive: line 40
Run it only after tests pass.
- Very specific: line 44
Commit the Perigon.CLI release changes on the current development branch with a conventional emoji-prefixed message such as 🚀 release: …
- Very specific: line 47
add git tag v<version> to the release commit and push the tag.
- Very specific: line 49
If the nuget branch has unrelated commits or conflicts, stop before merging and report the exact divergence.
- Very specific: line 53
Commit and push only the release-related files in Perigon.docs.
“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
Perigon.CLI Release Workflow
Use this skill when releasing Perigon.CLI or when the user asks to package and publish a version. The NuGet publishing workflow runs automatically when origin/nuget receives a push.
Before editing
- Inspect
git statusin bothPerigon.CLIandPerigon.docsrepositories. - Preserve unrelated user changes. Stage only files belonging to the release.
- Confirm the exact current version from
src/Apps/CommandLine/CommandLine.csproj.
Release contents
- Unless the user specifies a version, increment only the patch component of
<Version>insrc/Apps/CommandLine/CommandLine.csproj. - Keep
src/Apps/Dashboard/Dashboard.csprojon the same version. - Update
<PackageReleaseNotes>with only the changes being released. - Update the matching Chinese and English pages under
Perigon.docs/Content/docs/Perigon, normally the command-line page and the version update notes. Keep their structure and meaning aligned. - Add or update reusable release guidance in this skill and
Contribution.mdwhen the workflow changes.
Validation
Run the focused tests for the changed feature, then the full test project:
dotnet test tests/StudioMod.Tests/CoreMod.Tests.csproj --configuration Release --verbosity minimalThe CI-equivalent package/studio build is:
pwsh ./scripts/PublishToLocal.ps1 -withStudio:$truePublishToLocal.ps1 reads the tracked src/Apps/CommandLine/ShareDlls.txt when packaging Studio and removes the listed duplicate DLLs. If project dependencies change, run scripts/CheckSharedDlls.ps1 to refresh the list and commit the updated file.
Run it only after tests pass; it creates local publish/package artifacts and may install the package locally.
Branch handoff
- Commit the Perigon.CLI release changes on the current development branch with a conventional emoji-prefixed message such as
🚀 release: prepare Perigon.CLI 10.1.12. - Push that branch if it is the requested source branch.
- Fetch
origin/nuget, verify it has no unexpected divergence, merge the release commit into a localnugetbranch, and pushnugetwithout force-pushing. - add git tag
v<version>to the release commit and push the tag.
If the nuget branch has unrelated commits or conflicts, stop before merging and report the exact divergence. Do not reset, discard, or force-push user work.
Docs repository
Commit and push only the release-related files in Perigon.docs; leave any pre-existing uncommitted documentation changes untouched. Verify both zh-CN and en-US pages before handing off.
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.