agentleFS
Sign inStart free
PyModelPyModel/designer-skill/.claude/skills/release/SKILL.md

release

Skill46 starsChanged 47 days agoMITView on GitHub

Cut and publish a designer-skill-mcp release (maintainers only).

  • Commits and pushes

196 other projects use a version of this.

Adopted by

Most recently taken up by

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.
  • MicrosoftSkill

    create-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

  • GrinvSkill

    changelog-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 AzureSkill

    component-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-devSkill

    launch-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

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 0

    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
  1. Very specific:

    Add Co-authored-by or agent attribution to commits or tags.

    line 49

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

release

Repo-local maintainer skill; it is not shipped to plugin users.

Pipeline

scripts/release.sh prepares and tags; .github/workflows/publish.yml publishes from a clean checkout of the tag.

./scripts/release.sh "Release notes"          # next minor: 0.17.0 → 0.18.0
./scripts/release.sh 0.17.1 "Hotfix notes"    # explicit x.y.z (v0.17.1 also accepted)

release.sh:

  1. Preflight: on main, clean tree, in sync with origin/main, gh authenticated, claude CLI present, version not already on npm.
  2. node scripts/versions.mjs sync <version> writes the version to package.json, the lockfile, server.json, the three plugin manifests, the pinned mcp.json and the doc pins (@pymodel/designer-skill-mcp@x.y.z), then versions.mjs check.
  3. claude plugin validate --strict, npm ci, build, generated-asset drift check, checks/core.mjs, npm run typecheck, npm test, clean-install tarball smoke.
  4. Commits only the release files, tags v<version>, pushes main and the tag.

Rerunning after a partial run is safe: an existing tag at HEAD resumes at the push.

PUBLISH_LOCAL=1 ./scripts/release.sh "Notes" publishes to npm from this machine's npm login (no provenance) before pushing the tag. It builds, tests and smoke-tests a clean worktree of the tag first. npm processes uploads asynchronously; the CI npm job waits up to 10 minutes for the version and then skips it. It is now only a fallback: the npm trusted publisher is configured (2026-09-24), so a plain ./scripts/release.sh lets CI publish with provenance.

publish.yml (on v*.*.* tags) re-verifies versions against the tag, rebuilds and tests, then:

  • npm publish --provenance via npm trusted publishing (OIDC, no token; skipped if the version exists). One-time setup on npmjs.com: package Settings → Trusted publisher → GitHub Actions, PyModel/designer-skill, workflow publish.yml, environment npm, with direct publishing allowed (npm trust github … --allow-publish). Configured 2026-09-24 (saving needs the owner's security key; npm trust github cannot do it from a 2FA-bypass token). If the CI publish fails, the job waits for a PUBLISH_LOCAL=1 publish;
  • MCP registry mcp-publisher validate + publish via GitHub OIDC (fatal on failure). The namespace is case-sensitive: io.github.PyModel/*;
  • gh release create from the tag notes (skipped if it exists).

A failed publish run is re-run from the Actions tab; each step skips completed work.

Verify

node scripts/versions.mjs check
npm view @pymodel/designer-skill-mcp version
gh release view v<version>

Do not

  • Publish from a local working tree (npm publish by hand) — the tag is the source of truth.
  • Edit version fields by hand; use versions.mjs sync.
  • Add Co-authored-by or agent attribution to commits or tags.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.

Check your setup, free