audit-xcode-security-settings
Audit and enable security-oriented Xcode build settings. Progressively enables compiler warnings, static analyzer checkers, and Enhanced Security features. Use when: user wants to secure their Xcode project, audit security settings, enable hardening, review security posture of build configuration, set up security-focused static analysis, enable static analysis, improve warning coverage, harden diagnostics, or catch more bugs at compile time in C/C++/Objective-C/Swift. SKIP: network security (TLS/ATS), code signing, privacy APIs.
npx skills add superagents-lab/xcode27-skills --skill audit-xcode-security-settings --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Audit Xcode Security Settings Assess an Xcode project's security posture and progressively enable security build settings and entitlements — from broadly applicable warnings through Enhanced Security hardening. ## Tool Preferences When `GetTargetBuildSettings` writes its output to a saved file due to a token limit, see `references/reading-build-settings.md` for the schema and the filter script (`scripts/filter_build_settings.py`). Do not read the saved file linearly. When XcodeGlob, XcodeGrep, XcodeRead, and XcodeLS tools are available, ALWAYS use them. Do not fall back to Bash filesystem tools (`ls`, `find`, `cat`, `grep`) to learn about the project. They trigger extra permission prompts and bypass project scoping. - **XcodeGlob** for file discovery — `find` is forbidden for files inside the project. - **XcodeGrep** for content search — `grep`/`rg` is forbidden for files inside the project. - **XcodeRead** for file contents — `cat`/`Read` is forbidden for files registered in the project. - **XcodeLS** for directory listing — `ls` is forbidden for any path inside the project. **Project root and name are already in the system prompt context.** Do NOT run `ls` to "verify" the proje
- Tool Preferences
- Common Failure Modes
- Workflow
- Phase 0: Discovery
- Track Progress
- Phase 1: Analyze Project and Settings
- Phase 2: Apply Settings
- Phase 3: Inquire about Disabled Settings
- Phase 4: Validate Settings
- Phase 5: Report and Decision Document
- Phase 6: Optional Follow-up Steps
- User-Facing Interaction Guidelines
What does the audit-xcode-security-settings skill do?
Audit and enable security-oriented Xcode build settings. Progressively enables compiler warnings, static analyzer checkers, and Enhanced Security features. Use when: user wants to secure their Xcode project, audit security settings, enable hardening, review security posture of build configuration, set up security-focused static analysis, enable static analysis, improve warning coverage, harden diagnostics, or catch more bugs at compile time in C/C++/Objective-C/Swift. SKIP: network security (TLS/ATS), code signing, privacy APIs.
How do I install it?
Run `npx skills add superagents-lab/xcode27-skills --skill audit-xcode-security-settings --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From superagents-lab/xcode27-skills, a repository with 261 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.