How do I install the Rpce Release skill?

Run npx skillmds@latest add repoprompt/rpce-release in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rpce Release safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rpce Release?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rpce Release free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rpce Release?

repoprompt (@repoprompt) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rpce Release by repoprompt — Agent Skill

Name: Rpce Release
Rating: 4.5 (4 reviews)
Author: repoprompt

File contents

RepoPrompt CE Release

Use this skill when preparing a RepoPrompt CE release artifact or orienting a maintainer through a production release.

Contributor artifact

Run the secret-free lane:

make dev-release-preflight
make dev-release-artifact

For a local-only release-mode installation signed by the user's own dedicated self-signed identity, install Python 3 and double-click Install RepoPrompt CE Local Production.command in Finder, or use the coordinated CLI path:

CONFIRM_LOCAL_PRODUCTION_INSTALL=1 make dev-install-local-production

This app is not notarized and must not be distributed or uploaded to GitHub Releases.

Report the ZIP, SHA256SUMS, and external artifact manifest written under dist/. Confirm that the public candidate is universal arm64+x86_64, ad-hoc signed, intended for packaging validation, and not distributable. Debug and local self-signed packages remain host-native.

Maintainer publish

Read docs/releasing.md before publishing.

Use the environment-scoped GitHub Publish Release workflow for production draft creation. It requires an existing pushed tag and the release environment secrets documented there. Review the resulting ZIP, DMG, checksum, appcast, and artifact-manifest assets and require the fresh secret-free exact-helper packaged roundtrip to pass, then use the environment-scoped Promote Release workflow for the same tag. Promotion verifies and mirrors the existing reviewed assets, publishes both releases without rebuilding, resumes matching partial states, enforces a monotonically increasing stable build, and runs anonymous post-publish checks. Dispatch both workflows from protected main only after the release environment reviewer gate, main deployment restriction, and immutable v* tag ruleset are enabled, and GitHub Release immutability is enabled for both the source and updater repositories. Supply the SHA-256 digest of the reviewed source-draft SHA256SUMS file when dispatching promotion. Do not paste private keys, profiles, certificate exports, tokens, or passwords into logs or chat.

RepoPrompt CE starts its independent release history at 1.0.0 (1). Increment BUILD_NUMBER monotonically for every later public update. After changing version.env, run make release-sync-cli-version and commit the synchronized MCP CLI version before creating the release tag.

For an explicit private-source updater smoke test, use the maintainer-only Scripts/publish_public_update_test.sh helper documented in docs/releasing.md. It publishes only verified Developer ID signed, notarized ZIPs to the public artifact-only update repository.

Before a tag, commit, or push, run the repository-local $rpce-contribution-check skill and follow its approval requirements.

---name: rpce-releasedescription: Build or publish RepoPrompt CE release artifacts using the repository release scripts and GitHub workflows.---# RepoPrompt CE ReleaseUse this skill when preparing a RepoPrompt CE release artifact or orienting amaintainer through a production release.## Contributor artifactRun the secret-free lane:```bashmake dev-release-preflightmake dev-release-artifact```For a local-only release-mode installation signed by the user's own dedicatedself-signed identity, install Python 3 and double-click[`Install RepoPrompt CE Local Production.command`](../../../Install%20RepoPrompt%20CE%20Local%20Production.command)in Finder, or use the coordinated CLI path:```bashCONFIRM_LOCAL_PRODUCTION_INSTALL=1 make dev-install-local-production```This app is not notarized and must not be distributed or uploaded to GitHubReleases.Report the ZIP, `SHA256SUMS`, and external artifact manifest written under`dist/`. Confirm that the public candidate is universal `arm64+x86_64`, ad-hocsigned, intended for packaging validation, and not distributable. Debug andlocal self-signed packages remain host-native.## Maintainer publishRead [`docs/releasing.md`](../../../docs/releasing.md) before publishing.Use the environment-scoped GitHub **Publish Release** workflow for productiondraft creation. It requires an existing pushed tag and the `release`environment secrets documented there. Review the resulting ZIP, DMG, checksum, appcast, and artifact-manifest assetsand require the fresh secret-free exact-helper packaged roundtrip to pass, thenuse the environment-scoped **Promote Release** workflow for the sametag. Promotion verifies and mirrors the existing reviewed assets, publishesboth releases without rebuilding, resumes matching partial states, enforces amonotonically increasing stable build, and runs anonymous post-publish checks.Dispatch both workflows from protected `main` only after the `release`environment reviewer gate, `main` deployment restriction, and immutable `v*`tag ruleset are enabled, and GitHub Release immutability is enabled for boththe source and updater repositories. Supply the SHA-256 digest of the reviewedsource-draft `SHA256SUMS` file when dispatching promotion. Do not paste private keys,profiles, certificate exports, tokens, or passwords into logs or chat.RepoPrompt CE starts its independent release history at `1.0.0 (1)`.Increment `BUILD_NUMBER` monotonically for every later public update.After changing `version.env`, run `make release-sync-cli-version` and commit thesynchronized MCP CLI version before creating the release tag.For an explicit private-source updater smoke test, use the maintainer-only`Scripts/publish_public_update_test.sh` helper documented in[`docs/releasing.md`](../../../docs/releasing.md). It publishes only verifiedDeveloper ID signed, notarized ZIPs to the public artifact-only updaterepository.Before a tag, commit, or push, run the repository-local`$rpce-contribution-check` skill and follow its approval requirements.

Frequently asked questions

Rpce Release