app-intents-code-review
Reviews App Intents code for intent structure, entities, shortcuts, and parameters. Use when reviewing code with import AppIntents, @AppIntent, AppEntity, AppShortcutsProvider, or @Parameter.
What this skill does
# App Intents Code Review ## Quick Reference | Issue Type | Reference | |------------|-----------| | AppIntent protocol, perform(), return types | [references/intent-structure.md](references/intent-structure.md) | | AppEntity, EntityQuery, identifiers | [references/entities.md](references/entities.md) | | AppShortcutsProvider, phrases, discovery | [references/shortcuts.md](references/shortcuts.md) | | @Parameter, validation, dynamic options | [references/parameters.md](references/parameters.md) | ## Review Checklist - [ ] `perform()` marked with `@MainActor` if accessing UI/main thread resources - [ ] `perform()` completes within 30-second timeout (no heavy downloads/processing) - [ ] Custom errors conform to `CustomLocalizedStringResourceConvertible` - [ ] `EntityQuery.entities(for:)` handles missing identifiers gracefully - [ ] `EntityStringQuery` used if Siri voice input needed (not plain `EntityQuery`) - [ ] `suggestedEntities()` returns reasonable defaults for disambiguation - [ ] `AppShortcut` phrases include `.applicationName` parameter - [ ] Non-optional `@Parameter` has sensible defaults or uses `requestValue()` - [ ] `@IntentParameterDependency` not used on iOS 16 targets (crashes) - [ ] Phrases localized in `AppShortcuts.strings`, not `Localizable.strings` - [ ] App Intents defined in app bundle, not Swift Package (pre-iOS 17) - [ ] `isDiscoverable = false` for internal/widget-only intents ## When to Load References - AppIntent protocol implementation -> intent-structure.md - Entity queries, identifiers, Spotlight -> entities.md - App Shortcuts, phrases, discovery -> shortcuts.md - Parameter validation, dynamic options -> parameters.md ## Review Questions 1. Does `perform()` handle timeout limits for long-running operations? 2. Are entity queries self-contained (no `@Dependency` injection in Siri context)? 3. Do phrases read naturally and include the app name? 4. Are SwiftData models passed by `persistentModelID`, not directly? 5. Would migrating from SiriKit break existing user shortcuts? ## 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 type: the `AppIntent` / `AppEntity` / `EntityQuery` / `AppShortcutsProvider` (or equivalent) that contains the flagged code, not only a diff hunk or snippet. 3. **Platform or integration claim** (only if the finding depends on minimum iOS, Swift Package vs app target, `@IntentParameterDependency` availability, SiriKit migration, or `isDiscoverable` / extension placement) — You name one concrete artifact you inspected (for example `IPHONEOS_DEPLOYMENT_TARGET` or target membership in the Xcode project, `Package.swift` `platforms`, entitlements, or where the intent file lives) **or** you drop or downgrade the finding to an open question. 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.
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.