Bump Swift Version
Bump the version for the TinyClips Swift app across Info.plist, Info-MAS.plist, and project.pbxproj. Use this skill when you need to update the app version (e.g., from 1.8.0 to 1.9.0).
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Bump Swift Version when an AI agent needs a reusable SKILL.md workflow for this job: Bump the version for the TinyClips Swift app across Info.plist, Info-MAS.plist, and project.pbxproj. Use this skill when you need to update the app version (e.g., from 1.8.0 to 1.9.0).
When not to use it
Skip Bump Swift Version when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/bump-swift-version # Save SKILL.md to ~/.claude/skills/bump-swift-version/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/bump-swift-version/SKILL.md. For a shared project, commit the folder at .claude/skills/bump-swift-version/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Bump Swift Version skill for this task: When preparing a new release of the TinyClips macOS app. Confirm any required inputs or files before making changes.
What supports this recommendation?
81/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 87/100
- Practical detail
- 92/100
- Source evidence
- 60/100
- Source signals
- 72/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotinferred
The skill text mentions Copilot or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Bump Swift App Version
This skill updates the TinyClips macOS app version across all version configuration files in a single command.
## What it does
The skill automatically updates the following files with the new version number:
- `mac/TinyClips/Info.plist` - `CFBundleShortVersionString` - `mac/TinyClips/Info-MAS.plist` - `CFBundleShortVersionString` (Mac App Store variant) - `mac/TinyClips.xcodeproj/project.pbxproj` - All 4 `MARKETING_VERSION` entries (Debug/Release for Direct and MAS builds)
## When to use
- When preparing a new release of the TinyClips macOS app - When you need to update the version before building or submitting to the Mac App Store - To keep all version references in sync across the project
## How to use
1. Request the version bump in chat: ``` /bump-swift-version 1.9.0 ```
2. Provide the new version in format `X.Y.Z` (e.g., `1.9.0`, `2.0.0`). `X.Y` (e.g., `2.0`) is also accepted.
## Files included
- `bump-swift-version.sh` - Shell script that performs the version updates
## Step-by-step procedure
When asked to bump the Swift version:
1. **Run the script** from the repository root. It validates the version format and updates all three files together: if any of them cannot be updated, it fails and leaves all three untouched: ```bash .github/skills/bump-swift-version/bump-swift-version.sh 1.9.0 ``` 2. **Verify changes** - `git diff --stat` should show exactly the three files above with 6 changed lines (one per plist, four in `project.pbxproj`) 3. **Open a pull request, if one was requested** - Validate both mac schemes as described in `.github/copilot-instructions.md`, commit the three files as `Bump macOS version to X.Y.Z`, and create the PR
Always use the script instead of editing the plists with `PlistBuddy -c "Set ..."` or `plutil -replace`. Those rewrite the whole file and reorder its keys; the script changes only the version line.
## Example
**Request:** ``` Bump the Swift app version to 1.9.0 ```
**Result:** - Info.plist: CFBundleShortVersionString = 1.9.0 - Info-MAS.plist: CFBundleShortVersionString = 1.9.0 - project.pbxproj: All MARKETING_VERSION = 1.9.0
## Notes
- The version format must be `X.Y.Z` or `X.Y` (e.g., 1.9.0, 1.10.2, 2.0) - This updates both the direct distribution and Mac App Store variant - All 4 build configurations (Debug Direct, Release Direct, Debug MAS, Release MAS) are updated - Changes are made directly to the files; no commit is created automatically
Intended uses
- When preparing a new release of the TinyClips macOS app
- When you need to update the version before building or submitting to the Mac App Store
- To keep all version references in sync across the project
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.