macos-build
Skill90 starsChanged 5 months agoMITView on GitHub
Build a native macOS app using xcodebuild from the command line. Use this skill whenever the user asks to build, compile, or check if their macOS project compiles successfully. Also use it when the user asks to fix build errors, verify changes compile, or run a debug build. Trigger on phrases like "build the app", "does it compile", "run xcodebuild", "fix build errors", or even just "build".
3 other projects use a version of this.
Adopted by
Most recently taken up by
- lingyired/status-trioword for word, first seen Nov 8, 2026
- fayazara/macos-app-skillsword for word, first seen May 27, 2026
- miketikh/claude-skillz-conversiontheir own version, first seen Oct 21, 2025
Other versions3 projects use a version of this.
Word for word · 2
- lingyired/status-trio★ 1.8k100% same
- fayazara/macos-app-skills★ 660100% same
Edited · 0
None found.
Wrote their own version · 1
- miketikh/claude-skillz-conversion★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- macos-auto-updateSkill
- macos-notch-uiSkill
- macos-patternsSkill
- macos-releaseSkill
- macos-settings-uiSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Before building, locate the Xcode project or workspace:
- Distinctive: line 31
Use this command template, replacing the project path and scheme:
- Distinctive: line 57
If the output is empty or unclear, re-run without the grep filter to get full output for diagnosis.
- Distinctive: line 61
After making code changes, if the user asks to verify they compile
- Distinctive: line 62
When the user explicitly says "build", "compile", or "check if it builds"
- Distinctive: line 63
After fixing build errors, to confirm the fix worked
- Distinctive: line 67
If the project targets a beta SDK (e.g., macOS 26 Tahoe), you may need to point to the beta Xcode:
- Distinctive: line 73
Check which Xcode is available:
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Build macOS App
Build any native macOS Xcode project from the command line using xcodebuild.
Finding the Project
Before building, locate the Xcode project or workspace:
find . -maxdepth 2 -name "*.xcodeproj" -o -name "*.xcworkspace" | head -5Then list available schemes:
xcodebuild -list -project "YourApp.xcodeproj" 2>/dev/null | grep -A 20 "Schemes:"Build Command
Use this command template, replacing the project path and scheme:
DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer xcodebuild build \
-project "YourApp.xcodeproj" \
-scheme "YourApp" \
-configuration Debug \
-destination "platform=macOS" \
2>&1 | grep -E "(BUILD SUCCEEDED|BUILD FAILED|error:)" | head -20For workspaces (projects with SPM dependencies or CocoaPods):
DEVELOPER_DIR=/Applications/Xcode.app/Contents/Developer xcodebuild build \
-workspace "YourApp.xcworkspace" \
-scheme "YourApp" \
-configuration Debug \
-destination "platform=macOS" \
2>&1 | grep -E "(BUILD SUCCEEDED|BUILD FAILED|error:)" | head -20Interpreting Results
- BUILD SUCCEEDED -- the build passed, report success to the user.
- BUILD FAILED with
error:lines -- read each error, identify the source file and line, and help the user fix them. After fixing, re-run the build to verify. - If the output is empty or unclear, re-run without the grep filter to get full output for diagnosis.
When to Build
- After making code changes, if the user asks to verify they compile
- When the user explicitly says "build", "compile", or "check if it builds"
- After fixing build errors, to confirm the fix worked
Xcode Beta Toolchains
If the project targets a beta SDK (e.g., macOS 26 Tahoe), you may need to point to the beta Xcode:
DEVELOPER_DIR=/Applications/Xcode-beta.app/Contents/Developer xcodebuild build ...Check which Xcode is available:
ls /Applications/ | grep -i xcodeCommon Build Failures
| Error | Fix |
no such module 'Sparkle' | SPM dependency not resolved. Try xcodebuild -resolvePackageDependencies first |
no signing identity found | Set CODE_SIGN_IDENTITY="" and CODE_SIGNING_ALLOWED=NO for command-line builds |
SDK "macosx" cannot be located | Wrong DEVELOPER_DIR. Check Xcode installation path |
scheme not found | Run xcodebuild -list to see available schemes |
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

