Index of every page on this site: llms.txt
All skills
openclaw avatar

/release-clawpatch

@f74b1ef
by openclawopenclaw/clawpatch821 stars
119
Run it yourself

clawpatch release: version/changelog, CI, npm publish, GitHub release, verify.

Use this Skill: https://skilld.dev/gh/openclaw/clawpatch/release-clawpatch

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈24 tokens for metadata: the name and description. ≈1k when used: this file. ≈52 more on demand in 1 file.

Description uses 1.2% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈98 characters, or 1.2%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Clawpatch Release

Scope

Release ~/Projects/clawpatch as the public npm package clawpatch.

Use $npm and $one-password rules for registry auth. Keep all op and npm secret work inside one persistent tmux session and temp npmrc. Never print tokens, passwords, or OTPs.

Workflow

  1. Start clean on main.

    • cd ~/Projects/clawpatch
    • git status --short --branch
    • git pull --ff-only
    • Confirm target version is not already tagged or released: git tag --list "vX.Y.Z" and gh release view vX.Y.Z --repo openclaw/clawpatch.
    • Confirm npm state: npm view clawpatch version dist-tags time --json.
  2. Prep release files.

    • Set package.json version to target.
    • Change top changelog section from Unreleased to X.Y.Z - YYYY-MM-DD.
    • Ensure release notes are the changelog body for that version and include all user-facing changes.
    • Run pnpm install --lockfile-only; commit lockfile only if it actually changes.
  3. Prove locally before publishing.

    • Run pnpm typecheck && pnpm lint && pnpm format:check && pnpm test && pnpm build && pnpm pack:smoke.
    • Fix failures before continuing.
  4. Commit and push release prep.

    • Commit with committer "chore(release): X.Y.Z" CHANGELOG.md package.json [pnpm-lock.yaml].
    • git push origin main.
    • Watch CI/CodeQL for the release commit:
      • gh run list --repo openclaw/clawpatch --branch main --commit <sha> --json databaseId,workflowName,status,conclusion,url,headSha
      • gh run view <run_id> --repo openclaw/clawpatch --json status,conclusion,url,jobs
    • Do not publish until release-commit CI and CodeQL are green.
  5. Publish npm.

    • Use a temp npmrc, never the default user npmrc.
    • First try npm whoami; if unauthenticated, use npm web login in the tmux session:
      • NPM_CONFIG_USERCONFIG="$tmp_npmrc" npm login --auth-type=web --registry=https://registry.npmjs.org/
      • Open/approve browser login if prompted.
    • For publish, fetch a fresh OTP from the npmjs 1Password item inside the same tmux session.
    • Publish with NPM_CONFIG_USERCONFIG="$tmp_npmrc" npm publish --access public --otp "$NPM_OTP".
    • Clean temp npmrc/work dirs after publish.
    • If publish says the version already exists, verify npm metadata and continue only if it matches the release commit/package contents.
  6. Verify npm before GitHub release.

    • npm view clawpatch@X.Y.Z version dist-tags dist.tarball dist.integrity time --json
    • Required: version is X.Y.Z, latest points to X.Y.Z, tarball URL exists, integrity exists, publish time exists.
  7. Tag and create GitHub release.

    • Build release notes from changelog plus npm/proof:
      • npm version page
      • registry tarball
      • integrity string
      • CI and CodeQL run URLs
      • local proof command
    • Use temp files for public GitHub bodies.
    • git tag -a vX.Y.Z <release_sha> -m "vX.Y.Z"
    • git push origin vX.Y.Z
    • gh release create vX.Y.Z --repo openclaw/clawpatch --title "vX.Y.Z" --notes-file "$notes"
  8. Release verify.

    • npm view clawpatch@X.Y.Z version dist-tags.latest dist.tarball dist.integrity time.X.Y.Z --json
    • gh release view vX.Y.Z --repo openclaw/clawpatch --json tagName,url,body,isDraft,isPrerelease
    • Confirm release body contains changelog notes, npm version link, tarball, integrity, and CI/proof.
    • Confirm tag points at the release commit: git rev-list -n1 vX.Y.Z.
  9. Post-release closeout.

    • Add next patch section at top of CHANGELOG.md: ## X.Y.(Z+1) - Unreleased.
    • Commit with committer "docs(changelog): open X.Y.(Z+1)" CHANGELOG.md.
    • Push main.
    • Watch closeout CI until green.
    • Final: git checkout main && git pull --ff-only && git status --short --branch.

Notes

  • Do not create the GitHub release before npm publish is verified; the release body must include npm proof.
  • If npm auth scripts fail, keep the same tmux session. Do not start a second secret session unless the first is unusable.
  • Avoid broad secret inspection. Query exact npmjs fields only.
  • Public gh comments/releases should use temp --body-file / --notes-file, not inline quoted bodies.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts24d3 checks · Risk SAFE
  • Gen Agent Trust Hub24d

    The skill automates software releases for the 'clawpatch' project, involving GitHub, npm, and 1Password. It incorporates security best practices for secret handling but is vulnerable to indirect prompt injection through its ingestion of local changelog files.

  • Socket24d

    No alerts

  • Snyk24d

    Risk: LOW · No issues

Signed by skilld at f74b1ef. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 6 months ago

README badge

README badge for openclaw/clawpatch/release-clawpatch