kmshdev/claude-swift-toolkit/code-analyzer

Project Context

• Recent changes: !git diff --name-only HEAD~3 2>/dev/null || echo "no git history"
• Swift version: !swift --version 2>&1 | head -1 || echo "swift not found"

Code Analyzer (Read-Only)

Structured Swift/macOS code analysis protocol. Read-only — no file modifications.

Lifecycle Position

Phase 5 (Review). Load before swiftui-view-refactor for architectural overview. For deep line-by-line analysis, use audit-context-building.

Xcode MCP Orientation

When Xcode is available through this plugin's bundled bridge, prefer the MCP tools over shelling out to Xcode directly:

1. Use XcodeListWindows to identify the active workspace tab.
2. Use XcodeGlob, XcodeGrep, and XcodeRead to map the codebase you are

reviewing.

1. Use XcodeRefreshCodeIssuesInFile when compiler diagnostics are relevant to

the review findings.

Analysis Protocol

Step 1 — Map the Entry Point

1. Find the @main App struct or entry point
2. Identify window scenes (WindowGroup, Settings, MenuBarExtra)
3. Trace the root navigation structure (NavigationSplitView, TabView)

Step 2 — Trace the Module Graph

1. List all Swift source files grouped by directory/feature
2. Identify dependencies between modules (imports, protocol conformances)
3. Map state ownership: which types own @Observable models, which receive them
4. Identify services/repositories and their injection pattern

Step 3 — Identify Architecture Pattern

Classify the codebase:

• MV (Model-View): Views consume models directly via @State, @Environment, @Query
• MVVM: Separate ViewModel classes mediate between Model and View
• TCA: Reducers, Store, Actions, State
• Hybrid: Mix of patterns across features

Note consistency — are all features using the same pattern?

Review Checklist

1. Code Organization — PASS / WARN / FAIL

2. State Management — PASS / WARN / FAIL

3. Error Handling — PASS / WARN / FAIL

4. Performance — PASS / WARN / FAIL

5. Concurrency — PASS / WARN / FAIL

6. Security — PASS / WARN / FAIL

7. Test Coverage — PASS / WARN / FAIL

Output Format

For each section, provide:

### [Section Name] — [PASS/WARN/FAIL]
 
**Summary:** One-line assessment.
 
**Findings:**
- [file_path:line] Description of issue
- [file_path:line] Description of issue
 
**Recommendation:** What to fix and in what order.

Cross-References

• If the apple-design-system plugin is installed, use its swiftui-ui-patterns

review checklist for SwiftUI-specific review

• For view structure refactoring, load swiftui-view-refactor
• For deep line-by-line analysis, load audit-context-building