Menu
Increment app version numbers. Use when user asks to bump version, increment version, or prepare a release.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Custom themed scrollbars for macOS WKWebView apps. Use when styling scrollbars in the native macOS app, fixing scrollbar theming issues, implementing custom scroll containers that work in WKWebView, or debugging scroll position persistence issues with tabs.
Guide for implementing keyboard navigation and focus indicators across macOS native app (WKWebView) and web browser versions. Use when adding focusable elements, fixing Tab key navigation, or debugging focus ring visibility issues.
Guide for working with workspace tabs, tab management, and duplicate tab prevention. Use when fixing tab bugs, adding tab features, or working with openTab/addNewTab functions.
Design patterns and component guidelines for the Nomendex UI. Use when building dialogs, layouts, or fixing visual/layout issues.
Guide for working with the ProseMirror-based notes editor. Use when editing notes feature code, fixing editor bugs, working with todos/checkboxes, wiki_links, decorations, or serialization.
Create new Claude Skills with proper structure, frontmatter, and best practices. Use when the user wants to create a skill, build a skill, make a new skill, or scaffold skill files.
| name | version-bump |
| description | Increment app version numbers. Use when user asks to bump version, increment version, or prepare a release. |
When this skill is invoked:
mac-app/macos-host/Info.plist0.2.0-alpha.10 → 0.2.0-alpha.11)11 → 12)All version information comes from:
mac-app/macos-host/Info.plist
Two version fields:
0.2.0-alpha.4)5) - must be incremented for every releasemac-app/macos-host/Info.plist<key>CFBundleShortVersionString</key>
<string>0.2.0-alpha.5</string>
<key>CFBundleVersion</key>
<string>6</string>
Important: Always increment CFBundleVersion. Sparkle uses this numeric value to determine if an update is available.
Follow semantic versioning with optional pre-release identifiers:
MAJOR.MINOR.PATCH for stable releases (e.g., 1.0.0)MAJOR.MINOR.PATCH-alpha.N for alpha releases (e.g., 0.2.0-alpha.4)MAJOR.MINOR.PATCH-beta.N for beta releases (e.g., 0.2.0-beta.1)Info.plist (both fields)v{version}| Location | Source | Purpose |
|---|---|---|
| Info.plist | Manual edit | Single source of truth |
| GitHub Release | Workflow reads Info.plist | Release tag and assets |
| Appcast XML | Workflow reads Info.plist | Sparkle update detection |
| UI Sidebar | /api/version endpoint | Display to user |
The sidecar serves version info at /api/version:
{
"version": "0.2.0-alpha.4",
"buildNumber": "5"
}
This reads from Info.plist at runtime, checking multiple paths for dev vs bundled app.
Sparkle compares CFBundleVersion (build number) to determine updates:
56This is why CFBundleVersion must always increase, even for the same display version.