القائمة
Prepare a release by bumping the build number, collecting user-facing changes into a changelog, and committing the result.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use after making changes to visually validate the app in the iOS Simulator. Builds, installs, launches the app, then uses screenshots and accessibility descriptions to verify the change looks and behaves correctly.
Use when working with the Racket backend, adding or modifying RPC methods, or understanding the Racket-Swift communication layer. Covers define-rpc, Backend.swift codegen, and the Noise RPC framework.
Use when building, testing, or linting the Ruckus iOS app, regenerating the Tuist project, running tests, or adding new Swift files. Covers xcodebuild, tuist, make, swiftlint, and test workflows.
استنادا إلى تصنيف SOC المهني
| name | release |
| description | Prepare a release by bumping the build number, collecting user-facing changes into a changelog, and committing the result. |
| user-invocable | true |
Read current build number. Parse CURRENT_PROJECT_VERSION from
xcconfigs/Ruckus.xcconfig.
Let OLD = that value and NEW = OLD + 1.
Bump the build number. Update CURRENT_PROJECT_VERSION in both:
xcconfigs/Ruckus.xcconfigxcconfigs/RuckusWidgets.xcconfigSet the value to NEW in both files.
Collect changes. Run git log from the commit that last changed
CURRENT_PROJECT_VERSION (i.e. the previous bump) to HEAD.
Summarize user-visible changes. Skip CI, refactors, and changes to internals. Keep each entry to one short line.
Write the changelog. Create docs/changelogs/<BUILD>.md where <BUILD>
is NEW formatted as %05d (e.g. build 4 → 00004). Use this format:
# Build <NEW>
## Added
- Addition one.
- Addition two.
## Changed
- Change one.
- Change two.
## Fixed
- Fix one.
- Fix two.
## Removed
- Removal one.
- Removal two.
Commit. Stage the two xcconfig files and the new changelog, then commit with the message:
release: build <NEW>