release-clawpatch Skill
clawpatch release: version/changelog, CI, npm publish, GitHub release, verify. Published by openclaw in clawpatch.
Decision snapshot
Is this a fit?
Testing, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
24 days ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is release-clawpatch Skill?
clawpatch release: version/changelog, CI, npm publish, GitHub release, verify. Published by openclaw in clawpatch. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Testing use cases
Declared skill metadata
- Source file: .agents/skills/release-clawpatch/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use release-clawpatch Skill
- Use it for testing.
Built with
Editorial notes
Source
- Creator: openclaw
- Repository: openclaw/clawpatch
- Skill file: .agents/skills/release-clawpatch/SKILL.md
What it does
clawpatch release: version/changelog, CI, npm publish, GitHub release, verify.
Skill instructions
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
Verified compatibility and discovery
Frequently asked questions
What is release-clawpatch?
release-clawpatch is a open-source AI agent skill with Copy skill directory. clawpatch release: version/changelog, CI, npm publish, GitHub release, verify.
Who is release-clawpatch best for?
release-clawpatch is best for reusing agent instructions, scripts, and references, testing workflows.
How do I install release-clawpatch?
Install or run release-clawpatch using Copy skill directory. Check release-clawpatch for the latest setup command.
Is release-clawpatch actively maintained?
release-clawpatch may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
