Index of every page on this site: llms.txt
All skills
rshankras avatar

/release-review

@f958982
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/rshankras/claude-code-apple-skills/release-review

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈62 tokens for metadata: the name and description. ≈1.2k when used: this file. ≈9.5k more on demand in 5 files.

Description uses 3.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈250 characters, or 3.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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:

# 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, 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:

# Release Review: [App Name]

**Platform**: macOS / iOS / Universal
**Distribution**: App Store / Direct Download / TestFlight
**Review Date**: [Date]

## Summary

| Priority | Count |
|----------|-------|
| Critical | X |
| High | X |
| Medium | X |
| Low | X |

---

## 🔴 Critical Issues (Must Fix)

Issues that will cause rejection, crashes, or security vulnerabilities.

### [Category]: [Issue Title]

**File**: `path/to/file.swift:123`
**Impact**: [Why this matters]

**Current Code**:
```swift
// problematic code

Suggested Fix:

// fixed code

🟠 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

  1. [Critical] [First thing to fix]
  2. [Critical] [Second thing to fix]
  3. [High] [Third thing to fix] ...

## Priority Classification

### 🔴 Critical
- Security vulnerabilities (credential exposure, injection)
- Crashes or data loss scenarios
- App Store rejection causes
- Privacy violations
- Hardcoded secrets or spoofed identifiers

### 🟠 High
- Poor error handling (silent failures)
- Missing user consent or transparency
- Accessibility blockers
- Missing required Info.plist keys
- Broken functionality

### 🟡 Medium
- Incomplete onboarding
- Suboptimal UX patterns
- Missing empty states
- Performance concerns
- Minor accessibility issues

### 🟢 Low
- Code style improvements
- Additional features
- Polish and refinement
- Documentation improvements

## Platform-Specific Considerations

### macOS
- Menu bar app window activation (`NSApp.activate`)
- Sandbox exceptions justification
- Notarization requirements
- Hardened runtime
- Developer ID signing
- DMG/installer considerations

### iOS
- App Tracking Transparency
- Privacy nutrition labels
- Launch screen requirements
- Export compliance
- In-app purchase requirements
- TestFlight configuration

## References

- **security-checklist.md** - Detailed security review items
- **privacy-checklist.md** - Privacy and data handling
- **ux-polish-checklist.md** - User experience review
- **distribution-checklist.md** - Release and distribution
- **api-design-checklist.md** - Network and API patterns

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill acts as a pre-release review utility for macOS and iOS applications. It is structurally secure and contains no malicious instructions, obfuscation, or data exfiltration paths. It has a low-risk exposure to indirect prompt injection due to its processing of external project files, but its capabilities are strictly bounded to read-only tools.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • Runlayer9mo

    6/6 files flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at f958982. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 4 months ago
What it can do
Reads files
last_verified
2026-07-16
review_by
2027-06-22
os_version
iOS 27 / macOS 27
All 3 allowed tools
ReadGlobGrep

README badge

README badge for rshankras/claude-code-apple-skills/release-review