watchos-code-review — Claude Code skill: review and install
The watchos-code-review skill reviews watchOS code for lifecycle, complications, WatchConnectivity, and resource limits. Use it when checking WatchKit or SwiftUI app code.
Apache-2.0 137 installs ★ 89 updated 2026-09-15
npx skills add existential-birds/beagle --skill watchos-code-review -a claude-codeWhat watchos-code-review does
The skill reviews watchOS code that uses WatchKit, WKExtension, WKApplicationDelegate, or WCSession. It checks app lifecycle and background behavior, extended runtime sessions, ClockKit and WidgetKit complications, iPhone–Watch communication, memory, battery use, and performance constraints.
Its checklist is backed by reference sections for lifecycle, complications, connectivity, and performance. Every reported issue must include [FILE:LINE], cover the surrounding implementation, and include a concrete watchOS or device-pairing artifact when the claim depends on platform behavior. A finding without that evidence should remain a review question.
The checks include delegate assignment before WCSession.activate(), reachability before sendMessage, transferUserInfo for critical data, background downloads through URLSessionDownloadTask, future timeline entries, and workout-session recovery. Reports use the format [FILE:LINE] ISSUE_TITLE.
What it helps with
- review watchOS app lifecycle handling
- spot missing or invalid
WidgetKittimeline entries - check
WCSessionmessage and file-transfer logic - find background-task, memory, and battery issues
- enforce file-and-line evidence for review findings
Example prompts for the agent
- Review this watchOS code and report every issue as
[FILE:LINE] ISSUE_TITLE. - Check whether
WCSession, background tasks, and file transfers are handled correctly between iPhone and Apple Watch. - Review this
WidgetKitcomplication for future timeline entries and Smart Stack relevance.
How to install watchos-code-review
1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill watchos-code-review -a claude-code2Manually: put the files in place
~/.claude/skills/watchos-code-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/watchos-code-review/
1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill watchos-code-review -a codex2Manually: put the files in place
.agents/skills/watchos-code-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill watchos-code-review -a cursor2Manually: put the files in place
.cursor/skills/watchos-code-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install existential-birds/beagle plugins/beagle-ios/skills/watchos-code-review2Manually: put the files in place
.github/skills/watchos-code-review/SKILL.md1Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill watchos-code-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/existential-birds/beagle --path plugins/beagle-ios/skills/watchos-code-reviewManually: put the files in place
.devin/skills/watchos-code-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add existential-birds/beagle --skill watchos-code-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about watchos-code-review
How do I install watchos-code-review in Claude Code?
Run npx skills add existential-birds/beagle --skill watchos-code-review -a claude-code, then check ~/.claude/skills/watchos-code-review/SKILL.md.
What does watchos-code-review do?
It reviews watchOS code for lifecycle and background behavior, ClockKit and WidgetKit complications, WatchConnectivity, memory, battery, and performance constraints. Findings include a file and line location.
What does the skill check in WCSession code?
It checks delegate setup before activate(), reachability before sendMessage, transferUserInfo for critical data, and synchronous file handling before a delegate callback returns.
Source text
SKILL.md · Apache-2.0
--- name: watchos-code-review description: 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. --- # 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)
© existential-birds · Apache-2.0 · existential-birds/beagle