Skip to main content
skill CX Codex

cloudkit-code-review — Claude Code skill: what it does, how to install

cloudkit-code-review audits CloudKit code for custom zones, batching, error backoff, and asset size limits.

Apache-2.0 127 installs ★ 89 updated 2026-09-15

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add existential-birds/beagle --skill cloudkit-code-review -a claude-code
Open on GitHub

What cloudkit-code-review does

The skill triggers on code importing CloudKit, CKContainer, CKRecord, or CKShare. It spots sync pitfalls such as missing retryAfterSeconds backoff, unhandled CKErrorPartialFailure, and single-record saves executed instead of CKModifyRecordsOperation.

Issues are formatted as [FILE:LINE] ISSUE_TITLE. The reviewer checks the surrounding method scope and verifies claims against deployment artifacts like Info.plist or entitlements before reporting.

What it helps with

  • Catch missing retryAfterSeconds handling and rate-limit backoffs
  • Find record payloads exceeding 1MB stored without CKAsset
  • Flag individual saves that should use CKModifyRecordsOperation
  • Verify custom zone usage required for CKShare

Example prompts for the agent

  • Review SyncManager.swift for CloudKit error handling and backoff
  • Audit our CKShare implementation and zone setup
  • Check DataStore.swift for UI dispatches outside the main thread

How to install cloudkit-code-review

1Skills CLI (Vercel)

npx skills add existential-birds/beagle --skill cloudkit-code-review -a claude-code

2Manually: put the files in place

~/.claude/skills/cloudkit-code-review/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/cloudkit-code-review/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about cloudkit-code-review

How do I install cloudkit-code-review in Claude Code?

Run npx skills add existential-birds/beagle --skill cloudkit-code-review -a claude-code.

What does cloudkit-code-review do?

It reviews Apple CloudKit implementations for missing batching, unhandled partial failures, and incorrect zone usage.

How does the skill verify findings?

It requires inspecting the full enclosing function and matching configuration artifacts like entitlements before outputting an issue.

Source text

SKILL.md · Apache-2.0
---
name: cloudkit-code-review
description: Reviews CloudKit code for container setup, record handling, subscriptions, and sharing patterns. Use when reviewing code with import CloudKit, CKContainer, CKRecord, CKShare, or CKSubscription.
---

# CloudKit Code Review

## Quick Reference

| Issue Type | Reference |
|------------|-----------|
| CKContainer, databases, zones, entitlements | [references/container-setup.md](references/container-setup.md) |
| CKRecord, references, assets, batch operations | [references/records.md](references/records.md) |
| CKSubscription, push notifications, silent sync | [references/subscriptions.md](references/subscriptions.md) |
| CKShare, participants, permissions, acceptance | [references/sharing.md](references/sharing.md) |

## Review Checklist

- [ ] Account status checked before private/shared database operations
- [ ] Custom zones used (not default zone) for production data
- [ ] All CloudKit errors handled with `retryAfterSeconds` respected
- [ ] `serverRecordChanged` conflicts handled with proper merge logic
- [ ] `CKErrorPartialFailure` parsed for individual record errors
- [ ] Batch operations used (`CKModifyRecordsOperation`) not individual saves
- [ ] Large binary data stored as `CKAsset` (records have 1MB limit)
- [ ] Record keys type-safe (enums) not string literals
- [ ] UI updates dispatched to main thread from callbacks
- [ ] `CKAccountChangedNotification` observed for account switches
- [ ] Subscriptions have unique IDs to prevent duplicates
- [ ] CKShare uses custom zone (sharing requires custom zones)

## When to Load References

- Reviewing container/database setup or zones -> container-setup.md
- Reviewing record CRUD or relationships -> records.md
- Reviewing push notifications or sync triggers -> subscriptions.md
- Reviewing sharing or collaboration features -> sharing.md

## Output Format

Report issues using: `[FILE:LINE] ISSUE_TITLE`

Examples:
- `[AppDelegate.swift:24] CKContainer not in custom zone`
- `[SyncManager.swift:156] Unhandled CKErrorPartialFailure`
- `[DataStore.swift:89] Missing retryAfterSeconds backoff`

## Review Questions

1. What happens when the user is signed out of iCloud?
2. Does error handling respect rate limiting (`retryAfterSeconds`)?
3. Are conflicts resolved or does data get overwritten silently?
4. Is the schema deployed to production before App Store release?
5. Are shared records in custom zones (required for CKShare)?

## 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 type or function that owns the CloudKit work (for example the `CKOperation` subclass usage, completion handler chain, or `CKRecord` lifecycle), not only a diff hunk or isolated snippet.
3. **CloudKit or deployment claim** (only if the finding depends on container identifiers, public vs private database choice, custom zone requirement, iCloud account state, entitlements, or production schema) — You name one concrete artifact you inspected (for example `com.apple.developer.icloud-container-environment` or container ID in the entitlements file, `CKContainer.default()` vs custom identifier in source, `Info.plist` / target capability, or evidence that schema is deployed) **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.

© existential-birds · Apache-2.0 · existential-birds/beagle

Similar skills

All skills for Code review and refactoring →

From the same set68

The whole set →
swiftdata-code-review swiftdata-code-review reviews SwiftData code for model relationships, query predicates, actor concurrency, and schema migrations. Works on .swift files. CX Codex +1 136installs howto-docs The howto-docs skill shapes task-focused how-to guides with prerequisites, actionable steps, result checks, and troubleshooting for readers who already know the product. CX Codex +1 135installs deepagents-code-review deepagents-code-review reviews Deep Agents code and flags what breaks agents at runtime: interrupt_on with no checkpointer, backends with no store. CX Codex +1 134installs healthkit-code-review healthkit-code-review walks HealthKit code through a fixed sequence: authorization, queries, observers, background delivery. Handy when you are the one reviewing health data work. CX Codex +1 134installs prometheus-go-code-review The prometheus-go-code-review skill reviews Prometheus instrumentation in Go, covering metric types, labels, naming, and registration. Use it when checking prometheus/client_golang code. CX Codex +1 126installs review-skill-improver review-skill-improver reviews code-review feedback logs, spots recurring rejection patterns, and proposes changes to review skills. Use it after feedback has accumulated and you want to refine review rules. CX Codex +1 125installs elixir-code-review elixir-code-review reviews Elixir files for OTP conventions, security caveats, and idiomatic style across .ex and .exs code. CX Codex +1 124installs app-intents-code-review app-intents-code-review reviews Swift App Intents code for intent structure, shortcuts phrases, entity queries, and iOS deployment quirks. CX Codex +1 124installs

Project sponsors

Companies that keep this analytics open