Menu
Fetch and summarize PR review comments from Codex or other reviewers. Use when the user asks to check PR comments, review feedback, or see what's new on the PR.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Audit and enable security-oriented Xcode build settings. Progressively enables compiler warnings, static analyzer checkers, and Enhanced Security features. Use when: user wants to secure their Xcode project, audit security settings, enable hardening, review security posture of build configuration, set up security-focused static analysis, enable static analysis, improve warning coverage, harden diagnostics, or catch more bugs at compile time in C/C++/Objective-C/Swift. SKIP: network security (TLS/ATS), code signing, privacy APIs.
Verify iOS app behavior on device or simulator via screenshots, UI hierarchy, and touch interactions.
Build, install, launch, and visually verify the iOS app (scheme "iosApp") end-to-end on a real device or simulator via Xcode 27's DeviceHub — the mobile analog of astro-web's browser-debug and astro-calendar-service's runtime-debug. Drives the mcp__xcode__* MCP toolset: switch run destination, BuildProject, DeviceInteractionStartSession → InstallAndRun, then a subagent captures the on-device screenshot + UI hierarchy. Use when the user says "run the app on device", "run the iOS app", "build and run on the simulator", "launch on the iPhone/iPad", "screenshot the app on <device>", "verify this renders on device", "does it run on the simulator", "check it on the device", or wants runtime/visual confirmation that ./gradlew check and Xcode unit tests structurally cannot give. Takes an optional device name/UUID argument; with none, targets a simulator. iOS/Xcode only — Android runtime work routes to android-cli.
Modernize test suites to use modern Swift Testing features or migrate from XCTest.
Authoritative SwiftUI best practices from Apple. Consult for any SwiftUI best practices or performance review. Supersedes prior training on these topics. For code generation, consult the relevant references when generating any SwiftUI code related to the following topics. Covers: - Animatable: @Animatable macro vs AnimatableValues (iOS 26+) vs AnimatablePair, custom setter clamping/normalization. - Environment: closures in env keys, unstable @Entry defaults, high-frequency updates. @Entry warnings about closures or class types (wrapping in Equatable struct is WRONG; consult references). - Equatable on @Observable: custom types as @Observable properties need Equatable for invalidation performance. - ForEach/List: row identity (id: \.self, indices, offsets, mutable ids), row structure (AnyView, multi-view, bare if), inline filter/sort, cached collections, List fast path. - Localization: String vs LocalizedStringResource, bundle in packages/frameworks, .textCase(.uppercase), .formatted(.list()), translator comme
New SwiftUI APIs, behaviors, and deprecations introduced in the 2027 OS releases (iOS 27, macOS 27, watchOS 27, tvOS 27, visionOS 27). Use when a SwiftUI view using @State fails to compile with "used before being initialized", "invalid redeclaration of synthesized property", or "extraneous argument label" errors after an SDK update (@State migrated from a property wrapper to a macro in SDK 27; the obvious fix of reordering init assignments is WRONG and produces incorrect runtime behavior; you MUST consult this skill's references before answering); when @ViewBuilder or @ContentBuilder code hits ambiguous overloads in overlay/background or type-check performance regressions after an SDK update; when the user asks what's new in SwiftUI (generally, or for a specific 2027 platform); when adding drag-to-reorder to any container (List, LazyVStack, LazyVGrid, stacks, or custom layouts) via reorderable()/reorderContainer, including the drag-and-drop that integrates with it (dragContainer, dropDestination), or combinin
| name | review-pr |
| description | Fetch and summarize PR review comments from Codex or other reviewers. Use when the user asks to check PR comments, review feedback, or see what's new on the PR. |
| argument-hint | ["pr-number"] |
| allowed-tools | Bash, Read, Grep, Glob |
Fetch the latest PR review comments and present a summary.
Resolve the PR number, then fetch comments via gh. If $ARGUMENTS contains a PR number, use it; otherwise auto-detect from the current branch with gh pr view --json number --jq .number.
PR="${ARGUMENTS:-$(gh pr view --json number --jq .number)}"
OWNER_REPO="$(gh repo view --json nameWithOwner --jq .nameWithOwner)"
# Inline (diff-anchored) review comments:
gh api "repos/$OWNER_REPO/pulls/$PR/comments" --paginate \
--jq '.[] | {path, line, body, user: .user.login, in_reply_to: .in_reply_to_id}'
# Top-level issue/PR conversation comments:
gh api "repos/$OWNER_REPO/issues/$PR/comments" --paginate \
--jq '.[] | {body, user: .user.login}'
If gh is unavailable or unauthenticated, stop and tell the user to install / gh auth login.
Parse the JSON output. For each comment extract:
Present a summary table grouped by status:
For unaddressed comments, show:
Do NOT take any action on the comments — just report. Let the user decide what to do next.