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:
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, certificate validation)
- Input validation (injection prevention)
- Entitlements audit
- Hardened runtime (macOS)
Phase 3: Privacy Review
Load and apply: privacy-checklist.md
Key areas:
- Data collection transparency
- Privacy manifest (iOS 17+)
- User consent flows
- Third-party SDK disclosure
- GDPR compliance basics
Phase 4: UX Polish Review
Load and apply: ux-polish-checklist.md
Key areas:
- First launch / onboarding
- Empty states and error handling
- Loading states
- Text truncation and accessibility
- Platform-specific UX patterns
Phase 5: Distribution Review
Load and apply: distribution-checklist.md
Key areas:
- Bundle identifier format
- Code signing configuration
- Info.plist completeness
- App icons
- Platform-specific requirements (notarization, App Store)
Phase 6: API Design Review
Load and apply: api-design-checklist.md
Key areas:
- User-Agent headers (honest identification)
- Error handling patterns
- Token expiration handling
- Rate limiting
- Offline handling
Output Format
Present findings in this structure:
Suggested Fix:
🟠 High Priority (Should Fix)
Issues that significantly impact user experience or trust.
[Same format as above]
🟡 Medium Priority (Fix Soon)
Issues that should be addressed but won't block release.
[Same format as above]
🟢 Low Priority / Suggestions
Nice-to-have improvements and polish.
[Same format as above]
✅ Strengths
What the app does well:
- [Strength 1]
- [Strength 2]
- [Strength 3]
Recommended Action Plan
- [Critical] [First thing to fix]
- [Critical] [Second thing to fix]
- [High] [Third thing to fix] ...


