release-review_skill

Overview

This skill performs a senior developer–level pre-release audit for macOS and iOS apps, detecting security, privacy, UX, and distribution issues with actionable fixes. It targets problems that cause App Store rejections, security vulnerabilities, or poor user experience, and produces a prioritized, developer-friendly action plan. Use it to harden apps before TestFlight, notarization, or public release.

How this skill works

I inspect the project structure to determine platform and app type, then run focused checks across six phases: project discovery, security, privacy, UX polish, distribution, and API design. Findings are categorized by priority (Critical, High, Medium, Low) and include file references, impact statements, and concrete suggested fixes. The output is a short, actionable review that you can use directly to triage and remediate issues before submission.

When to use it

• Preparing an app for App Store submission or TestFlight distribution
• Before notarization or direct macOS distribution
• When you want a critical, senior-developer review of security and privacy
• If you need to reduce risk of App Store rejection
• When you want a prioritized, actionable checklist before shipping

Best practices

• Run the review after a release candidate build so file paths and Info.plist content are stable
• Fix all critical security and privacy issues first, then address high-priority UX and distribution items
• Include concrete code examples or stack traces when a crash or vulnerability is reported
• Keep Info.plist, entitlements, and signing configuration consistent between CI and local builds
• Document any sandbox exceptions, third-party SDKs, and user data flows for reviewers

Example use cases

• A developer wants to ensure no hardcoded secrets, insecure network calls, or Keychain misuse remain
• QA needs a checklist of issues that could trigger App Store rejection for an iOS release
• Product manager requests a prioritized action plan covering privacy disclosures and consent flows
• Engineering lead wants UX polish items (onboarding, empty states, accessibility) identified before launch
• A macOS app preparing for notarization needs checks for hardened runtime and signing configuration