القائمة
Ship a BetterCmdTab release end to end. Use when the user wants a new version or beta published on GitHub.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
استنادا إلى تصنيف SOC المهني
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/rokartur/BetterCmdTab --skill releaseيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
عرض SKILL.md
Contract for adding or changing a persisted setting in BetterCmdTab. Use when touching Preferences.swift, a settings pane, or any Switcher.* UserDefaults key.
Witness BetterCmdTab product-source changes at the live macOS surface when a diff needs end-to-end runtime evidence.
Keep Localizable.xcstrings in lockstep with the code. Use whenever code adds, edits, or removes any user-facing string, or when LocalizationCatalogTests fails.
| name | release |
| description | Ship a BetterCmdTab release end to end. Use when the user wants a new version or beta published on GitHub. |
One command does the heavy lifting; this skill is the order of operations and the failure points around it.
Working tree clean on main, and the unit suite green:
xcodebuild -scheme "BetterCmdTab Debug" -destination 'platform=macOS' test
scripts/set_version.sh --show prints the current version. MAJOR tracks
the macOS year; tags are bare (26.4.3, 26.0-beta.1 — no v prefix on new
tags).
scripts/set_version.sh <version> # sets MARKETING_VERSION and auto-commits "chore: bump …"
Skip for betas — build_release.sh --beta derives the next beta.N from
existing GitHub tags itself.
Produce the release body with the release-changelog skill and save it to a
file (e.g. notes.md in the scratchpad). The body is the GitHub Release
description; its headings are parsed by build_release.sh, so the canonical
structure from that skill is mandatory.
--notes takes the notes text, not a path — pass the file through cat
or the literal filename becomes the release body:
scripts/build_release.sh --auto-release --notes "$(cat notes.md)" # stable
scripts/build_release.sh --beta --auto-release --notes "$(cat notes.md)" # beta (published as prerelease)
Step 0 is scripts/release_quality_gate.sh: a Release-configuration compile
that fails on high-risk concurrency/Sendable warnings, plus (stable only) the
localization audit — fix the reported issue, don't bypass the gate; it exists
so a known-bad build never burns an archive + notarization slot. Signing
needs the Developer ID Application: Artur Rok (N529W98U62) certificate and
the BetterCmdTabNotarization notarytool profile. Without them use
--skip-notarization (dev build only — it refuses --auto-release).
Artifacts land in build/release/. Each build stamps a fresh
CURRENT_PROJECT_VERSION (app target only); --skip-build-bump disables
that.
When not using --auto-release:
gh release create <tag> -R rokartur/BetterCmdTab \
--title "BetterCmdTab <version>" --notes-file notes.md # add --prerelease for betas
Complete when: the GitHub release exists with the notarized artifacts attached and the notes match the release-changelog format.