swift-review
- Repo stars 0
- Author updated Live
- Author repo skills-registry
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: swift-review
description: Review Swift/iOS code: SwiftUI, Combine, UIKit, App Store guidelines and iOS architecture Use wh…
category: engineering
runtime: no special runtime
---
# swift-review output preview
## PART A: Task fit
- Use case: Review Swift/iOS code: SwiftUI, Combine, UIKit, App Store guidelines and iOS architecture Use when this capability is needed. <!-- tomevault:4.0:skill_md:2026-05-23 --> runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to Use / Review Checklist / Architecture” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Review Swift/iOS code: SwiftUI, Combine, UIKit, App Store guidelines and iOS architecture Use when this capability is needed. <!-- tomevault:4.0:skill_md:2026-05-23 --> runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “When to Use / Review Checklist / Architecture” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “When to Use / Review Checklist / Architecture”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: swift-review
description: Review Swift/iOS code: SwiftUI, Combine, UIKit, App Store guidelines and iOS architecture Use wh…
category: engineering
source: tomevault-io/skills-registry
---
# swift-review
## When to use
- Review Swift/iOS code: SwiftUI, Combine, UIKit, App Store guidelines and iOS architecture Use when this capability is…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to Use / Review Checklist / Architecture” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "swift-review" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to Use / Review Checklist / Architecture
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Swift / iOS Code Review
When to Use
- Reviewing Swift/iOS code (SwiftUI, UIKit, Combine)
- Evaluating iOS architecture (MVVM, TCA, VIPER)
- App Store compliance review
- iOS performance and memory review
Review Checklist
Architecture
- MVVM or TCA architecture consistently applied
- View models don't import UIKit/SwiftUI
- Protocol-oriented design for dependencies
- Coordinator pattern for navigation (if UIKit)
-
@EnvironmentObject/@StateObjectused correctly
Swift Best Practices
- Value types (
struct) preferred over reference types (class) -
letpreferred overvar(immutability) - Guard clauses for early returns
-
Result<Success, Failure>for error handling -
Codablefor JSON parsing (not manual parsing) -
async/awaitinstead of completion handlers (iOS 15+) - Property wrappers for common patterns
- Access control (
private,internal,public) enforced
SwiftUI
- Views are small and composable (< 50 lines body)
-
@Statefor local,@Bindingfor parent-child,@ObservedObjectfor injected - No heavy computation in
body(use.task {}modifier) - Preview providers for all views
- Accessibility modifiers (
.accessibilityLabel,.accessibilityHint) - Dark mode support verified
Memory & Performance
- No retain cycles (
[weak self]in closures) -
Instrumentsprofiled for leaks - Images resized to display size (not full resolution)
- TableView/CollectionView cell reuse
- Background tasks for heavy work (
DispatchQueue.global()) - Core Data batch operations for large datasets
App Store Guidelines
- No private APIs used
- In-App Purchase for digital goods (not external links)
- Privacy manifest (
PrivacyInfo.xcprivacy) included - Required device capabilities declared
- App Transport Security exceptions justified
- No hardcoded test data in release builds
Output Format
## iOS Review: [Module]
**Health Score**: X/10
### Issues | Improvements | Architecture NotesSource: camilooscargbaptista/cto-toolkit — distributed by TomeVault.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review