watchos-code-review
Reviews watchOS code for app lifecycle, complications (ClockKit/WidgetKit), WatchConnectivity, and performance constraints. Use when reviewing code with import WatchKit, WKExtension, WKApplicationDelegate, WCSession, or watchOS-specific patterns.
What this skill does
# watchOS Code Review ## Quick Reference | Issue Type | Reference | |------------|-----------| | App lifecycle, scenes, background modes, extended runtime | [references/lifecycle.md](references/lifecycle.md) | | ClockKit, WidgetKit, timeline providers, Smart Stack | [references/complications.md](references/complications.md) | | WCSession, message passing, file transfer, reachability | [references/connectivity.md](references/connectivity.md) | | Memory limits, background refresh, battery optimization | [references/performance.md](references/performance.md) | ## Review Checklist - [ ] SwiftUI App protocol used with `@WKApplicationDelegateAdaptor` for lifecycle events - [ ] `scenePhase` read from root view (not sheets/modals where it's always `.active`) - [ ] `WKExtendedRuntimeSession` started only while app is active (not from background) - [ ] Workout sessions recovered in `applicationDidFinishLaunching` (not just delegate) - [ ] Background tasks scheduled at least 5 minutes apart; next scheduled before completing current - [ ] `URLSessionDownloadTask` (not `DataTask`) used for background network requests - [ ] WidgetKit used instead of ClockKit for watchOS 9+ complications - [ ] Timeline includes future entries (not just current state); gaps avoided - [ ] `TimelineEntryRelevance` implemented for Smart Stack prioritization - [ ] WCSession delegate set before `activate()`; singleton pattern used - [ ] `isReachable` checked before `sendMessage`; `transferUserInfo` for critical data - [ ] Received files moved synchronously before delegate callback returns ## When to Load References - Reviewing app lifecycle, background modes, or extended sessions -> lifecycle.md - Reviewing complications, widgets, or timeline providers -> complications.md - Reviewing WCSession, iPhone-Watch communication -> connectivity.md - Reviewing memory, battery, or performance issues -> performance.md ## Output Format Report issues using: `[FILE:LINE] ISSUE_TITLE` Examples: - `[WatchApp.swift:18] WKExtendedRuntimeSession started while app not active` - `[ConnectivityManager.swift:42] WCSession.activate() before delegate assignment` - `[ComplicationTimeline.swift:67] Timeline has no future entries` ## Hard gates (before reporting) Complete **in order** for each finding you intend to report. Do not advance until the pass condition is satisfied. 1. **Location artifact** — The finding includes `[FILE:LINE]` (or a line range) copied from the current file contents; the path resolves in this repo. 2. **Scope read** — You read the full surrounding unit: the `View` body, `WKApplicationDelegate` / scene method, `TimelineProvider` implementation, `WCSessionDelegate` callback, or workout/background task handler that owns the behavior—not only a diff hunk. 3. **watchOS or pairing claim** (only if the finding depends on background modes, complication/timeline contracts, `WCSession` reachability or transfer semantics, workout or extended runtime rules, or device-specific limits) — You name one concrete artifact you inspected (for example `Info.plist` / target capabilities for background modes, the `WK*` / `WCSession` call order in source, entitlements, or a subsection you read in the matching doc from [Quick Reference](#quick-reference)) **or** you downgrade the item to an open question in [Review Questions](#review-questions). 4. **Protocol** — Pre-report steps in [review-verification-protocol](../review-verification-protocol/SKILL.md) are satisfied for this item (no finding if they are not). Use the issue format `[FILE:LINE] ISSUE_TITLE` for each reported finding. Hard gate 4 is the full pre-report checklist for this skill’s review type. ## Review Questions 1. Is the app using modern SwiftUI lifecycle with delegate adaptor? 2. Are background tasks completing properly (calling `setTaskCompletedWithSnapshot`)? 3. Is UI update frequency reduced when `isLuminanceReduced` is true? 4. Are WatchConnectivity delegate callbacks dispatching to main thread? 5. Is `TabView` nested within another `TabView`? (Memory leak on watchOS)
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.