release
Skill4 starsChanged 4 months agoMITView on GitHub
Execute a pico-* package release. Use when creating version tags, updating changelogs, release notes, docs, and publishing.
- Reads credentials
- 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 repository12 other files it gives its agents.
- add-actuatorSkill
- add-appSkill
- add-authSkill
- add-celery-taskSkill
- add-componentSkill
- add-controllerSkill
- add-repositorySkill
- add-server-authSkill
- add-testsSkill
- add-validationSkill
- init-projectSkill
- pico-conventionsSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 5 are distinctive, and 5 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.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Before making any changes, verify the environment is ready and determine the correct version.
- Distinctive: line 60
Create the file with header and format preamble
- Very specific: line 62
Add nav entry to mkdocs.yml: - Changelog: CHANGELOG.md
- Very specific: line 79
Check against the floor tag, not against your venv: git -C ../pico-x show v<FLOOR>:src/pico_x/__init__.py | grep <SYMBOL>.
- Distinctive: line 87
Verify that upstream dependency was already released and tagged
- Very specific: line 88
Update pyproject.toml to >=UPSTREAM_VERSION before continuing
- Very specific: line 144
If gh release create fails with 401/403:
- Distinctive: line 146
If still failing, print manual URL for the user:
- Very specific: line 168
Update pyproject.toml dependency to >=NEW_VERSION
- Distinctive: line 185
If something goes wrong after push, follow these steps to undo:
“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 Checklist
Execute the following steps in order for releasing $ARGUMENTS.
0. Environment & Remote Validation
Before making any changes, verify the environment is ready and determine the correct version.
cd <package-dir>
git pull --rebase
git fetch --tags
git tag --sort=-v:refname | head -10git pull --rebase— sync with remotegit fetch --tags— pull all remote tags- List existing tags to identify the latest version
- Determine the next version based on semver:
- patch (X.Y.Z+1): bug fixes only
- minor (X.Y+1.0): new features, backward-compatible
- major (X+1.0.0): breaking changes
- Confirm the chosen version does NOT exist as a local or remote tag:
git tag -l "vX.Y.Z" # local git ls-remote --tags origin "vX.Y.Z" # remote - If the user provided a version in
$ARGUMENTS, verify it doesn't conflict - Verify
gh auth statusworks — if 401, tryunset GITHUB_TOKENand retry - Locate tools — check
.venv/bin/first, then system PATH:command -v ruff || .venv/bin/ruff --version command -v mkdocs || .venv/bin/mkdocs --version - Check
.gitignoreDOES blockreleases/— release notes are local-only; their content is used as the GitHub release body, never committed
1. Pre-flight
cd <package-dir>flagship-validation/preflight.sh— MANDATORY gate (docs-qa a cero + flagship hermetico). Add--level2(real infra + celery worker + JWT over uvicorn) if the release touches DB/broker/cache/auth/actuator.venv/bin/python -m pytest tests/ -v— all tests pass.venv/bin/coverage run -m pytest tests/ && .venv/bin/coverage report— coverage >= 95%ruff check src/ tests/(orruff check <pkg>/ tests/) — cleanruff format --check src/ tests/(orruff format --check <pkg>/ tests/) — clean- If
Makefileexists:make docker-e2e— Docker E2E tests pass
2. CHANGELOG.md
- If CHANGELOG.md is new:
- Create the file with header and format preamble
- Create symlink:
ln -sf ../CHANGELOG.md docs/CHANGELOG.md - Add nav entry to
mkdocs.yml:- Changelog: CHANGELOG.md
- Add new version section at the top (Keep a Changelog format)
- Format:
## [X.Y.Z] - YYYY-MM-DD - List changes under
### Added,### Changed,### Fixed,### Removedas applicable
3. Release Notes
- Create
releases/vX.Y.Z.mdwith:- Summary of what's new
- Feature list with descriptions
- Usage examples where appropriate
- Dependencies and compatibility notes
4. Dependency Chain Check
- PIN FLOOR vs IMPORTS (hard gate): every
from pico_x import SYMBOLinsrc/must exist in the MINIMUM version declared in pyproject. Check against the floor tag, not against your venv:git -C ../pico-x show v<FLOOR>:src/pico_x/__init__.py | grep <SYMBOL>. (pico-resilience 0.2.0 shipped importingConfigChanged— new in ioc 2.3.0 — while declaring>= 2.2.0; hotfix 0.2.1 the same day.) - If this package is a dependency of other pico-* packages:
- Identify which downstream
pyproject.tomlfiles reference this package - Note they will need
>=NEW_VERSIONafter this release
- Identify which downstream
- If this package depends on a pico-* package being released in the same session:
- Verify that upstream dependency was already released and tagged
- Update
pyproject.tomlto>=UPSTREAM_VERSIONbefore continuing
5. Documentation
- Update relevant docs files for new features
- Ensure nav entries exist in
mkdocs.ymlfor any new pages - Run
mkdocs build --strict— no warnings or errors fleet-scripts/docs-qa.py <repo>— zero findings (snippets compile, imported symbols exist, no emojis)- New features are VISIBLE: README section +
pico-conventionsskill section updated (a released feature nobody can read about does not exist). llms.txt/llms-full.txt regenerate on deploy — nothing manual
6. README.md
- Update feature lists, API tables, and examples for new functionality
- Ensure Quick Example reflects current public API
7. AGENTS.md
- Update file/module descriptions for new or changed files
- Update test count to match current suite
- Add descriptions for new concepts, models, or patterns
8. Commit
- Stage files explicitly (never
git add -A):git add CHANGELOG.md releases/vX.Y.Z.md docs/ mkdocs.yml README.md AGENTS.md \ src/ tests/ .gitignore pyproject.toml - Review staged changes:
git diff --cached --stat - Check for untracked release-related files:
git status --short - Commit:
git commit -m "chore(release): vX.Y.Z - tagline"
9. Tag
git tag vX.Y.Z10. Push
git push && git push --tags11. GitHub Release
gh release create vX.Y.Z --notes-file releases/vX.Y.Z.md --title "vX.Y.Z — Tagline"If gh release create fails with 401/403:
- Try:
unset GITHUB_TOKEN && gh release create ... - If still failing, print manual URL for the user:
https://github.com/OWNER/REPO/releases/new?tag=vX.Y.Z
12. Verify
gh run list --limit 5— wait for CI, docs, publish workflows to passgh release view vX.Y.Z— release exists with correct notes- Wait for the
publish-to-pypiworkflow to succeed, then verify the artifact:pip download <package>==X.Y.Z --no-deps -d /tmp/relcheck— the wheel filename must carry the exact clean version (no.postN, no.devN)
13. Post-release Downstream Updates
- Bump the pin in
pico-initializer/js/versions.js - New module? Register: conventions skill section, pico-skills README
table, initializer (tool/registry/index.html), AGENTS.md catalog in
pico-ioc, GitHub topics (
pico-framework+ funcionales +llms-txt) - For each downstream pico-* package that depends on this one:
- Update
pyproject.tomldependency to>=NEW_VERSION - Commit:
chore: bump PACKAGE>=NEW_VERSION - Push
- Update
- Update pico-initializer (single source of truth for generated projects):
- Bump the constraint for this package in
pico-initializer/js/versions.js(~=NEW_VERSIONfor 0.x packages; keep the<NEXT_MAJORcap for 1.x+) - Nothing to mirror:
test/Dockerfileandtest/Dockerfile.integrationderive their pre-installed deps fromversions.jsat build time - Commit:
chore: bump PACKAGE to NEW_VERSION in generated projects - Push (CI runs the integration suite against the new release before deploying)
- Bump the constraint for this package in
- Publish a new release train in
pico-bomwhen the validated set changes:- Copy the newest
YYYY.MM.txtto a new one, bump the changed pins, and add a row to the README table - never edit a published train, builds pin to it - CI validates the newest train automatically (
compose_check.py)
- Copy the newest
Rollback (if needed)
If something goes wrong after push, follow these steps to undo:
# Delete remote tag
git push origin :refs/tags/vX.Y.Z
# Delete local tag
git tag -d vX.Y.Z
# Delete GitHub release (if created)
gh release delete vX.Y.Z --yes
# Revert the commit (safe — don't use reset --hard)
git revert HEAD
git pushDoes 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.

