メニュー
Build or publish RepoPrompt CE release artifacts using the repository release scripts and GitHub workflows.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/repoprompt/repoprompt-ce --skill rpce-releaseコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Validate RepoPrompt CE contributions before committing or pushing. Use whenever an agent is about to create a commit, push the current branch, rewrite history, delete a branch or fork, or change GitHub-visible repository state. Enforces staged-index and outgoing-range secret scanning, repository guardrails, clean push boundaries, an explicit PR-ready lane for path-selected heavyweight validation, and explicit approval for destructive Git or visible live-app operations.
Plan, inventory, stage, execute, or review RepoPrompt CE's project-wide migration to Swift 6.2 concurrency checking and Swift 6 language mode. Use when auditing packages, targets, settings, diagnostics, unsafe escape hatches, migration phases, blockers, or validation evidence across the root and provider packages. Do not use for a bounded diagnostic repair unless it changes migration policy or sequencing.
Select, design, review, consolidate, or remove RepoPrompt CE tests, diagnostic harnesses, and smoke checks by regression value and maintenance cost. Use when the task centers on test, diagnostic, or smoke coverage, including whether a single regression test is worth committing. Do not use for feature or bug-fix work merely because it may need coverage, or for routine test or validation execution.
| name | rpce-release |
| description | Build or publish RepoPrompt CE release artifacts using the repository release scripts and GitHub workflows. |
Use this skill when preparing a RepoPrompt CE release artifact or orienting a maintainer through a production release.
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.
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.