Agent skill · Security

release-review

Senior developer-level release review for macOS/iOS apps. Identifies security, privacy, UX, and distribution issues with actionable fixes. Use when preparing an app for release, want a critical review, or before App Store submission.

rshankrasgithub.com/rshankrasGitHub ↗
claude-coderead-onlyMIT
Install
npx skills add rshankras/claude-code-apple-skills --skill release-review --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 5 KB
Bundled scripts: none
Allowed tools: ReadGlobGrep
Path: skills/release-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 589
Language: Swift

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Release Review for Apple Platforms Performs a comprehensive pre-release audit of macOS and iOS applications from a senior developer's perspective. Identifies critical issues that could cause rejection, security vulnerabilities, privacy concerns, and UX problems—with actionable fixes. ## When This Skill Activates Use this skill when the user: - Says "review for release", "release review", or "pre-release audit" - Asks for "senior developer review" or "critical review" - Mentions preparing for "App Store", "TestFlight", or "notarization" - Wants to know what "power users might complain about" - Asks to "review before shipping" or "check before release" ## Review Process ### Phase 1: Project Discovery First, understand the project: ```bash # Find project type Glob: **/*.xcodeproj or **/*.xcworkspace Glob: **/Info.plist Glob: **/project.pbxproj ``` Identify: - Platform (macOS, iOS, or both) - App type (standard app, menu bar app, widget, extension) - Distribution method (App Store, direct download, TestFlight) ### Phase 2: Security Review Load and apply: **security-checklist.md** Key areas: - Credential storage (Keychain patterns, no hardcoded secrets) - Data transmission (HTTPS, cer

What's inside
Steps it walks through
  1. When This Skill Activates
  2. Review Process
  3. Phase 1: Project Discovery
  4. Phase 2: Security Review
  5. Phase 3: Privacy Review
  6. Phase 4: UX Polish Review
  7. Phase 5: Distribution Review
  8. Phase 6: API Design Review
  9. Output Format
  10. Priority Classification
  11. 🔴 Critical
  12. 🟠 High
  13. 🟡 Medium
  14. 🟢 Low
Ships with 5 files
  • api-design-checklist.md
  • distribution-checklist.md
  • privacy-checklist.md
  • security-checklist.md
  • ux-polish-checklist.md
Commands it runs
Find project type
More from claude-code-apple-skills
All skills →
testingTDD and testing skills for iOS/macOS apps. Covers characterization tests, TDD workflows, test…Testing & QAcoverage-ratchetGate test coverage with a ratchet — a committed baseline that coverage may never drop below and…Testing & QAgeneratorsCode generator skills that produce production-ready Swift code for common app components. Use when…Data & Analyticsci-cd-setupGenerate CI/CD configuration for automated builds, tests, and distribution of iOS/macOS apps. Use…DevOps & Cloudapple-search-adsApple Search Ads campaign strategy for indie developers — paid acquisition, keyword bidding, budget…Content & Marketingsf-symbolsSF Symbols end-to-end — choosing and configuring the 7,000+ system symbols (rendering modes…Other
About this skill
What does the release-review skill do?

Senior developer-level release review for macOS/iOS apps. Identifies security, privacy, UX, and distribution issues with actionable fixes. Use when preparing an app for release, want a critical review, or before App Store submission.

How do I install it?

Run `npx skills add rshankras/claude-code-apple-skills --skill release-review --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 rshankras/claude-code-apple-skills, a repository with 589 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.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.