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. Use when this capability is needed.

tomevault-io bee6a05 2 files · 3.4 KB Updated Sep 17, 2026

Coding & Dev Tools

Install

Press C to copy

$ npx skillmds@latest add tomevault-io/watchos-code-review

Installs into ~/.claude/skills (or .claude/skills inside a project). Restart Claude Code to pick it up.

＋ Add to collection

README badge

[![SkillMD](https://skillmd.com/badge/tomevault-io/watchos-code-review.svg)](https://skillmd.com/skills/tomevault-io/watchos-code-review)

Trust & safety

Audits pending

Not yet audited · commit bee6a05

Works with: Claude Code Claude.ai OpenAI Codex +

File contents

watchOS Code Review

Quick Reference

Issue Type	Reference
App lifecycle, scenes, background modes, extended runtime	references/lifecycle.md
ClockKit, WidgetKit, timeline providers, Smart Stack	references/complications.md
WCSession, message passing, file transfer, reachability	references/connectivity.md
Memory limits, background refresh, battery optimization	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

Review Questions

Is the app using modern SwiftUI lifecycle with delegate adaptor?
Are background tasks completing properly (calling setTaskCompletedWithSnapshot)?
Is UI update frequency reduced when isLuminanceReduced is true?
Are WatchConnectivity delegate callbacks dispatching to main thread?
Is TabView nested within another TabView? (Memory leak on watchOS)

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: watchos-code-reviewdescription: 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. Use when this capability is needed.---# 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## Review Questions1. 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)---> Converted and distributed by [TomeVault](https://tomevault.io/claim/existential-birds) — claim your Tome and manage your conversions.

tomevault-io/skills-registry/tree/main/existential-birds--beagle--watchos-code-review commit bee6a0578a

Frequently asked questions

npx skillmds@latest add tomevault-io/watchos-code-review