swift-code-reviewer-skill 1.1.0 → 1.1.1

package/CHANGELOG.md

@@ -5,11 +5,25 @@ All notable changes to the Swift Code Reviewer Agent Skill will be documented in
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.1.1] - 2026-03-24
+
+### Fixed
+
+- Replace `install-skill.sh` with the correct installer for this skill (previously contained the XcodeBuildMCP installer by mistake)
+- Add `uninstall` command support to `install-skill.sh`
+
+## [1.1.0] - 2026-03-16
+
+### Added
+
+- increase adjusts from Dimillian skill and more scenarios to cover
+
 ## [1.0.0] - 2026-02-10
 
 ### Added
 
 #### Core Functionality
+
 - **Four-phase review workflow**: Context Gathering → Analysis → Report Generation → Delivery
 - **Multi-layer analysis** across 6 core categories:
   - Swift Best Practices (Swift 6+ concurrency, error handling, optionals)
@@ -20,6 +34,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - Project-Specific Standards (.claude/CLAUDE.md integration)
 
 #### Review Capabilities
+
 - **GitHub PR reviews** via `gh` CLI integration
 - **GitLab MR reviews** via `glab` CLI integration
 - **Git diff analysis** for uncommitted changes
@@ -28,6 +43,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Project standards validation** via .claude/CLAUDE.md
 
 #### Feedback System
+
 - **Severity classification**: Critical, High, Medium, Low
 - **Positive feedback** for good practices
 - **Refactoring suggestions** for improvements
@@ -36,6 +52,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Prioritized action items** for structured follow-up
 
 #### Reference Documentation (7,700+ lines)
+
 - **review-workflow.md** (1,131 lines): Complete review process and git integration
 - **swift-quality-checklist.md** (928 lines): Swift 6+ patterns and best practices
 - **swiftui-review-checklist.md** (909 lines): SwiftUI state management and modern APIs
@@ -46,12 +63,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **custom-guidelines.md** (852 lines): Project standards integration guide
 
 #### Integration Features
+
 - **swift-best-practices skill** integration for Swift 6+ language patterns
 - **swiftui-expert-skill** integration for SwiftUI best practices
 - **swiftui-performance-audit** integration for performance analysis
 - **Independent operation** with comprehensive built-in checklists
 
 #### Platform Support
+
 - Swift 6.0+
 - iOS 17+, macOS 14+, watchOS 10+, tvOS 17+, visionOS 1+
 - GitHub and GitLab integration
@@ -68,6 +87,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Features in Detail
 
 #### Swift Quality Checks
+
 - Actor isolation and MainActor usage
 - Sendable conformance validation
 - Data race prevention
@@ -78,6 +98,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Swift API Design Guidelines compliance
 
 #### SwiftUI Checks
+
 - @Observable pattern adoption (iOS 17+)
 - Property wrapper selection guide
 - NavigationStack vs NavigationView
@@ -88,6 +109,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Accessibility compliance
 
 #### Performance Checks
+
 - View update optimization
 - Equatable conformance for ViewModels
 - ForEach identity stability
@@ -98,6 +120,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Retain cycle prevention
 
 #### Security Checks
+
 - Keychain usage for credentials
 - Biometric authentication
 - HTTPS enforcement
@@ -109,6 +132,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Sensitive data logging prevention
 
 #### Architecture Checks
+
 - MVVM pattern validation
 - Repository pattern implementation
 - Dependency injection verification
@@ -119,6 +143,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Code organization (MARK comments, extensions)
 
 #### Project Standards
+
 - .claude/CLAUDE.md parsing and validation
 - Custom architecture pattern validation
 - Design system compliance (colors, fonts, spacing)
@@ -129,6 +154,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Templates and Examples
 
 #### Positive Feedback Templates
+
 - Modern API adoption
 - Architecture excellence
 - Code quality
@@ -137,12 +163,14 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Security awareness
 
 #### Issue Report Templates
+
 - Critical issues (security, crashes, data races)
 - High priority (performance, anti-patterns)
 - Medium priority (code quality, documentation)
 - Low priority (style, suggestions)
 
 #### Refactoring Suggestions
+
 - Extract subview
 - Simplify complex logic
 - Extract reusable component
@@ -151,18 +179,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Example Review Reports
 
 Provided complete examples for:
+
 - Reviewing uncommitted changes
 - Reviewing against project standards
 - Pull request reviews
 - File-specific reviews
 - Multi-file reviews
 
-## [1.1.0] - 2026-03-16
-
-### Added
-
-- increase adjusts from Dimillian skill and more scenarios to cover
-
 ## [Unreleased]
 
 ### Planned Features
@@ -187,6 +210,7 @@ Provided complete examples for:
 
 ## Version History Summary
 
+- **1.1.1** (2026-03-24): Fix incorrect `install-skill.sh` (was XcodeBuildMCP installer)
 - **1.1.0** (2026-03-16): Increase adjusts from Dimillian skill and more scenarios to cover
 - **1.0.0** (2026-02-10): Initial release with comprehensive review capabilities
 
@@ -216,6 +240,7 @@ See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines on proposing changes.
 ---
 
 **Note**: This skill follows [Semantic Versioning](https://semver.org/):
+
 - **MAJOR**: Incompatible API changes
 - **MINOR**: Backward-compatible functionality additions
 - **PATCH**: Backward-compatible bug fixes

package/README.md

@@ -1,545 +1,155 @@
 # Swift Code Reviewer Agent Skill
 
 [![GitHub Sponsors](https://img.shields.io/github/sponsors/Viniciuscarvalho?style=social)](https://github.com/sponsors/Viniciuscarvalho)
+[![npm version](https://img.shields.io/npm/v/swift-code-reviewer-skill)](https://www.npmjs.com/package/swift-code-reviewer-skill)
 
-A comprehensive code review skill for Claude that performs multi-layer analysis of Swift and SwiftUI code, combining Apple's best practices with project-specific coding standards.
+A code review skill for [Claude Code](https://docs.anthropic.com/en/docs/claude-code) that performs multi-layer analysis of Swift and SwiftUI code, combining Apple's best practices with your project-specific coding standards.
 
-## Features
-
-- 🔍 **Multi-Layer Analysis**: Combines Swift 6+ best practices, SwiftUI patterns, performance optimization, and security checks
-- 📋 **Project-Aware Reviews**: Reads `.claude/CLAUDE.md` to validate against project-specific standards and architecture patterns
-- 🎯 **Comprehensive Feedback**: Provides Critical/High/Medium/Low severity issues, positive feedback, and refactoring suggestions
-- 🔗 **Skill Integration**: Leverages existing `swift-best-practices`, `swiftui-expert-skill`, and `swiftui-performance-audit` skills
-- 📊 **Actionable Output**: Structured reports with file:line references, code examples, and prioritized action items
-- 🚀 **Platform Support**: Works with GitHub PRs, GitLab MRs, and local git changes
-
-## What It Reviews
-
-### Swift Quality
-
-- **Concurrency Safety**: Actor isolation, MainActor usage, Sendable conformance, data race prevention
-- **Error Handling**: Typed throws, Result types, proper error propagation
-- **Optionals**: Safe unwrapping, guard statements, no force unwraps
-- **Access Control**: Explicit access modifiers, minimal API surface
-- **Naming**: Swift API Design Guidelines compliance
-
-### SwiftUI Patterns
-
-- **State Management**: @Observable, @State, @Binding, @Environment usage
-- **Property Wrappers**: Correct wrapper selection for each use case
-- **Modern APIs**: NavigationStack, .task, latest SwiftUI features
-- **View Composition**: Extracted subviews, ViewBuilder patterns
-- **Accessibility**: Labels, hints, Dynamic Type support
-
-### Performance
-
-- **View Optimization**: Unnecessary updates, Equatable conformance
-- **ForEach Performance**: Stable identity, lazy loading
-- **Layout Efficiency**: GeometryReader usage, layout thrash
-- **Resource Management**: Image loading, memory leaks, async patterns
-
-### Security & Safety
-
-- **Input Validation**: Sanitization, bounds checking, type safety
-- **Sensitive Data**: Keychain storage, biometric authentication, secure logging
-- **Network Security**: HTTPS enforcement, certificate pinning, API key protection
-- **Permissions**: Privacy descriptions, permission timing, graceful handling
-
-### Architecture
-
-- **Pattern Compliance**: MVVM, MVI, TCA adherence
-- **Dependency Injection**: Constructor injection, protocol-based dependencies
-- **Code Organization**: File structure, MARK comments, logical grouping
-- **Testability**: Unit test coverage, mock usage, test structure
-
-### Project Standards
-
-- **Custom Guidelines**: Validates against `.claude/CLAUDE.md` rules
-- **Design System**: Color palette, typography, spacing token usage
-- **Error Patterns**: Custom error type conformance
-- **Testing Requirements**: Coverage thresholds, testing patterns
-
-## Installation
-
-### Option 1: NPX (Recommended)
-
-The fastest way to install — always fetches the latest version, no cloning or manual updates required:
+## Quick Start
 
 ```bash
 npx swift-code-reviewer-skill
 ```
 
-This automatically installs the skill to `~/.claude/skills/swift-code-reviewer-skill/`
-
-> **Tip:** Running `npx swift-code-reviewer-skill` again at any time will update to the latest version automatically.
-
-To uninstall:
-
-```bash
-npx swift-code-reviewer-skill uninstall
-```
-
-### Option 2: Clone This Repository
-
-```bash
-# Clone the skill
-git clone https://github.com/Viniciuscarvalho/swift-code-reviewer-skill.git ~/.claude/skills/swift-code-reviewer-skill
-
-# The skill is now ready to use!
-```
-
-### Option 3: Manual Installation
-
-1. Create the skill directory:
-
-```bash
-mkdir -p ~/.claude/skills/swift-code-reviewer-skill/references
-```
-
-2. Download the files from this repository into the directory
-
-3. Restart Claude or reload skills
-
-### Verify Installation
+That's it. The skill is installed and ready to use. Run it again anytime to update to the latest version.
 
-```bash
-ls ~/.claude/skills/swift-code-reviewer-skill/
-# Should show: SKILL.md, README.md, references/, and more
-```
+> No cloning, no manual setup. NPX always fetches the latest version automatically.
 
 ## Usage
 
 ![Swift Code Reviewer in action](assets/demo.png)
 
-### Basic Usage
-
-The skill automatically activates when you ask Claude to review Swift/SwiftUI code:
+Just ask Claude to review your code:
 
 ```
 Review this PR
-
 Review LoginView.swift
-
-Review my uncommitted changes
-
-Check if this follows our coding standards
-```
-
-### Review Specific Files
-
-```
-Review UserProfileView.swift
-```
-
-**What it does:**
-
-1. Reads `.claude/CLAUDE.md` for project standards
-2. Analyzes the file against all quality dimensions
-3. Provides structured feedback with severity levels
-4. Includes positive feedback and refactoring suggestions
-
-### Review Git Changes
-
-```
 Review my uncommitted changes
-```
-
-**What it does:**
-
-1. Runs `git diff` to identify changes
-2. Analyzes modified files
-3. Focuses on changed lines for efficiency
-4. Generates comprehensive review report
-
-### Review Pull Requests (GitHub)
-
-```
-Review PR #123
-```
-
-**What it does:**
-
-1. Fetches PR details using `gh pr view 123`
-2. Gets diff using `gh pr diff 123`
-3. Reads all changed files for context
-4. Generates detailed review with file:line references
-
-### Review Merge Requests (GitLab)
-
-```
-Review MR #456
-```
-
-**What it does:**
-
-1. Fetches MR details using `glab mr view 456`
-2. Gets diff and changed files
-3. Performs multi-layer analysis
-4. Generates actionable feedback
-
-### Review Against Custom Standards
-
-```
-Review LoginViewModel.swift against our coding standards
-```
-
-**What it does:**
-
-1. Reads `.claude/CLAUDE.md` and related architecture docs
-2. Extracts project-specific rules
-3. Validates code against both Apple and project standards
-4. Reports compliance and violations
-
-### Review Multiple Files
-
-```
 Review all ViewModels in the Features folder
+Check if this follows our coding standards
 ```
 
-**What it does:**
-
-1. Finds all matching files
-2. Analyzes each against architecture patterns
-3. Provides file-by-file review
-4. Summarizes common patterns and issues
-
-## How It Works
-
-The skill follows a **four-phase workflow**:
-
-### Phase 1: Context Gathering
-
-1. **Read Project Guidelines**
-   - Loads `.claude/CLAUDE.md` if it exists
-   - Reads related architecture documents
-   - Extracts custom coding standards
-
-2. **Identify Review Scope**
-   - Determines files to review (user-specified, git diff, PR/MR)
-   - Categorizes changes by type (UI, logic, tests)
-
-3. **Gather Context**
-   - Reads all files completely
-   - Understands broader context
-   - Identifies component relationships
-
-### Phase 2: Automated Analysis
-
-Runs parallel checks across **six core categories**:
-
-1. **Swift Best Practices** (leverages `swift-best-practices` skill)
-   - Concurrency safety and actor isolation
-   - API design and naming conventions
-   - Swift 6+ feature adoption
-
-2. **SwiftUI Quality** (leverages `swiftui-expert-skill`)
-   - State management patterns
-   - Modern API usage
-   - View composition
-
-3. **Performance** (leverages `swiftui-performance-audit`)
-   - View update optimization
-   - ForEach performance
-   - Resource management
-
-4. **Security & Safety**
-   - Force unwrap detection
-   - Sensitive data handling
-   - Network security
-
-5. **Architecture & Maintainability**
-   - Pattern compliance
-   - Dependency injection
-   - Testability
+The skill automatically activates, reads your `.claude/CLAUDE.md` for project standards, and generates a structured report with severity levels, code examples, and prioritized action items.
 
-6. **Project-Specific Standards**
-   - `.claude/CLAUDE.md` compliance
-   - Design system usage
-   - Custom error patterns
-
-### Phase 3: Report Generation
-
-1. **Categorizes findings** by severity (Critical, High, Medium, Low)
-2. **Includes positive feedback** for good practices
-3. **Adds refactoring suggestions** for improvements
-4. **Groups by file** and category
-5. **Provides code examples** for all issues
-
-### Phase 4: Delivery
-
-Generates a structured markdown report:
+### Example Output
 
 ```markdown
 # Code Review Report
 
 ## Summary
 
-- Files Reviewed: 5
-- Critical: 0
-- High: 2
-- Medium: 5
-- Low: 3
-- Positive Feedback: 8
-
-## Detailed Findings
-
-### File: LoginView.swift
+- Files Reviewed: 3 | Critical: 0 | High: 1 | Medium: 2 | Low: 1
 
-#### ✅ Positive Feedback
-
-1. Excellent use of @Observable for state management
+## File: LoginViewModel.swift
 
-#### 🟡 High Priority
+✅ **Excellent Modern API Usage** (line 12)
 
-1. Force unwrap detected at line 89 (potential crash)
+- Using @Observable instead of ObservableObject
 
-#### 💡 Refactoring Suggestions
+🟡 **Force Unwrap Detected** (line 89)
+Current: `let user = repository.currentUser!`
+Fix:
+guard let user = repository.currentUser else {
+logger.error("No current user")
+return
+}
 
-1. Consider extracting login form into separate view
+🔴 **Violates Design System Standard** (line 45)
+Current: `.foregroundColor(.blue)`
+Fix: `.foregroundColor(AppColors.primary)`
 
 ## Prioritized Action Items
 
-[Must fix, should fix, consider items]
+1. [Must fix] Remove force unwrap at line 89
+2. [Should fix] Use design system colors at line 45
 ```
 
-## Review Report Structure
-
-### Severity Levels
-
-| Severity     | Icon | Description                                         | Response Time           |
-| ------------ | ---- | --------------------------------------------------- | ----------------------- |
-| **Critical** | 🔴   | Security vulnerabilities, crashes, data races       | Must fix before merge   |
-| **High**     | 🟡   | Performance issues, anti-patterns, major violations | Should fix before merge |
-| **Medium**   | 🟠   | Code quality, documentation, minor violations       | Fix in current sprint   |
-| **Low**      | 🔵   | Style, suggestions, minor improvements              | Consider for future     |
-
-### Feedback Types
-
-**Positive Feedback** ✅
+## What It Reviews
 
-- Acknowledges good practices
-- Highlights excellent implementations
-- Recognizes proper patterns
+| Category              | Checks                                                                                                    |
+| --------------------- | --------------------------------------------------------------------------------------------------------- |
+| **Swift Quality**     | Concurrency safety, actor isolation, Sendable, error handling, optionals, access control, naming          |
+| **SwiftUI Patterns**  | @Observable, state management, property wrappers, NavigationStack, .task, view composition, accessibility |
+| **Performance**       | View updates, Equatable, ForEach identity, GeometryReader, lazy loading, memory leaks                     |
+| **Security**          | Keychain, input validation, HTTPS, certificate pinning, API key protection, sensitive data logging        |
+| **Architecture**      | MVVM/MVI/TCA compliance, dependency injection, code organization, testability                             |
+| **Project Standards** | `.claude/CLAUDE.md` rules, design system, custom error patterns, testing requirements                     |
 
-**Issues** 🔴🟡🟠🔵
+### Severity Levels
 
-- File and line references
-- Code examples (before/after)
-- Specific fixes with explanations
-- Links to documentation
+| Icon | Severity | Action                  |
+| ---- | -------- | ----------------------- |
+| 🔴   | Critical | Must fix before merge   |
+| 🟡   | High     | Should fix before merge |
+| 🟠   | Medium   | Fix in current sprint   |
+| 🔵   | Low      | Consider for future     |
 
-**Refactoring Suggestions** 💡
+## Platform Support
 
-- Proactive improvements
-- Modernization opportunities
-- Code simplification ideas
+- Works with **GitHub PRs** (`gh`), **GitLab MRs** (`glab`), and **local git changes**
+- Swift 6.0+ | iOS 17+ | macOS 14+ | watchOS 10+ | tvOS 17+ | visionOS 1+
 
 ## Project-Specific Standards
 
-The skill reads `.claude/CLAUDE.md` to understand your project's:
+Add a `.claude/CLAUDE.md` to your project and the skill will validate against your rules:
 
-- Architecture pattern (MVVM, MVI, TCA, etc.)
-- Dependency injection approach
-- Error handling patterns
-- Testing requirements
-- Design system guidelines
-- Navigation patterns
-- Custom naming conventions
-
-### Example .claude/CLAUDE.md
-
-````markdown
-# MyApp Coding Standards
+```markdown
+# MyApp Standards
 
 ## Architecture
 
-We use **MVVM with Coordinators**:
-
 - ViewModels MUST use @Observable (iOS 17+)
 - All dependencies MUST be injected via constructor
 - Views MUST NOT contain business logic
 
-## Error Handling
-
-All errors MUST conform to AppError:
-
-```swift
-protocol AppError: Error {
-    var message: String { get }
-    var code: Int { get }
-}
-```
-````
-
 ## Design System
 
 - Use AppColors enum ONLY
 - Use AppFonts enum ONLY
-- Use AppSpacing for all padding
 
 ## Testing
 
 - Minimum coverage: 80%
 - All ViewModels MUST have unit tests
-
-```
-
-The skill will validate your code against these standards and report violations.
-
-## Reference Documentation
-
-The skill includes comprehensive reference guides:
-
-- **review-workflow.md**: Step-by-step review process and git commands
-- **swift-quality-checklist.md**: Swift 6+ concurrency, error handling, optionals
-- **swiftui-review-checklist.md**: State management, property wrappers, modern APIs
-- **performance-review.md**: View optimization, ForEach performance, layout efficiency
-- **security-checklist.md**: Input validation, sensitive data, network security
-- **architecture-patterns.md**: MVVM, Repository, DI, Use Case, Coordinator patterns
-- **feedback-templates.md**: Review comment templates and severity guidelines
-- **custom-guidelines.md**: How to parse and validate `.claude/CLAUDE.md`
-
-## Integration with Other Skills
-
-This skill **leverages** three foundational skills:
-
-### swift-best-practices
-For Swift 6+ language patterns, concurrency, and API design
-- Loads when reviewing Swift language usage
-- References: `concurrency.md`, `swift6-features.md`, `api-design.md`
-
-### swiftui-expert-skill
-For SwiftUI state management and modern APIs
-- Loads when reviewing SwiftUI views
-- References: `state-management.md`, `modern-apis.md`, `view-composition.md`
-
-### swiftui-performance-audit
-For performance analysis
-- Loads when performance concerns identified
-- Runs focused audit on performance-sensitive paths
-
-**Note**: These skills should be installed separately for full functionality, but the code reviewer works independently with its own comprehensive checklists.
-
-## Examples
-
-### Example 1: Review Uncommitted Changes
-
-**Input:**
 ```
 
-Review my uncommitted changes
+## Alternative Installation
 
-````
+<details>
+<summary>Clone this repository</summary>
 
-**Output:**
-```markdown
-# Code Review Report
-
-## Summary
-- Files Reviewed: 3
-- Critical: 0
-- High: 1
-- Medium: 2
-- Low: 1
-- Positive Feedback: 5
-
-## File: LoginViewModel.swift
-
-✅ **Excellent Modern API Usage** (line 12)
-- Using @Observable instead of ObservableObject
-- Clean, modern pattern for iOS 17+
-
-🟡 **Force Unwrap Detected** (line 89)
-**Severity**: High
-**Issue**: Force unwrapping can crash if data is nil
-
-Current Code:
-```swift
-let user = repository.currentUser!
-````
-
-Recommended Fix:
-
-```swift
-guard let user = repository.currentUser else {
-    logger.error("No current user")
-    return
-}
+```bash
+git clone https://github.com/Viniciuscarvalho/swift-code-reviewer-skill.git ~/.claude/skills/swift-code-reviewer-skill
 ```
 
-```
+</details>
 
-### Example 2: Review Against Project Standards
+<details>
+<summary>Manual installation</summary>
 
-**Input:**
+```bash
+mkdir -p ~/.claude/skills/swift-code-reviewer-skill/references
 ```
 
-Review LoginView.swift against our coding standards
-
-````
+Download the files from this repository into the directory, then restart Claude.
 
-**Output:**
-```markdown
-# Project Standards Review
-
-## .claude/CLAUDE.md Compliance
+</details>
 
-✅ **Architecture Adherence**
-- Follows MVVM pattern correctly
-- No business logic in view
-- Dependencies injected properly
-
-🔴 **Violates Design System Standard** (line 45)
-**Project Guideline**: "Use AppColors enum ONLY. No hardcoded colors"
-
-Current Code:
-```swift
-.foregroundColor(.blue)  // ❌ Hardcoded
-````
-
-Expected Code:
-
-```swift
-.foregroundColor(AppColors.primary)  // ✅ Design system
-```
-
-Reference: .claude/CLAUDE.md:Design System
+<details>
+<summary>Uninstall</summary>
 
+```bash
+npx swift-code-reviewer-skill uninstall
 ```
 
-## Requirements
-
-- Claude Code CLI
-- Git (for reviewing diffs and PRs)
-- Optional: `gh` CLI for GitHub integration
-- Optional: `glab` CLI for GitLab integration
-- Swift 6.0+
-- iOS 17+, macOS 14+, watchOS 10+, tvOS 17+, or visionOS 1+
+</details>
 
-## Limitations
-
-- Cannot execute code or run tests (static analysis only)
-- Cannot access external systems or APIs
-- Limited to analyzing provided code or git-accessible code
-- Cannot detect runtime issues requiring execution
-- Performance analysis based on patterns, not profiling data
+## Integration with Other Skills
 
-For runtime analysis, use Instruments or other profiling tools alongside this skill.
+This skill optionally leverages **swift-best-practices**, **swiftui-expert-skill**, and **swiftui-performance-audit** for deeper analysis. It works independently with its own comprehensive checklists.
 
 ## Contributing
 
-Contributions are welcome! Here's how you can help:
-
-1. **Report Issues**: Found a bug or have a suggestion? Open an issue
-2. **Improve Checklists**: Add new patterns or update existing checks
-3. **Add Examples**: Contribute real-world review examples
-4. **Update Documentation**: Improve clarity and add use cases
-5. **Add Templates**: Create new feedback templates
-
-### Development
-
-To modify the skill:
-
 1. Edit `SKILL.md` for main skill logic
 2. Update reference files in `references/` for specific checklists
 3. Test with real Swift/SwiftUI code
@@ -547,34 +157,12 @@ To modify the skill:
 
 ## License
 
-MIT License - See [LICENSE](LICENSE) file for details
-
-## Acknowledgments
-
-- Inspired by Apple's Swift API Design Guidelines
-- Leverages best practices from the Swift and SwiftUI communities
-- Built on top of Claude's code analysis capabilities
-- Designed to complement existing Swift development skills
-
-## Support
-
-- **Issues**: [GitHub Issues](https://github.com/Viniciuscarvalho/swift-code-reviewer-skill/issues)
-- **Discussions**: [GitHub Discussions](https://github.com/Viniciuscarvalho/swift-code-reviewer-skill/discussions)
-
-## Version History
-
-### 1.0.0 (2026-02-10)
-- Initial release
-- Comprehensive Swift 6+ and SwiftUI review capabilities
-- Project-specific standards integration
-- Multi-layer analysis (6 categories)
-- Structured feedback with all severity levels
-- Integration with existing skills
-- 7,700+ lines of comprehensive documentation
+MIT License - See [LICENSE](LICENSE) file for details.
 
 ---
 
 **Made with ❤️ for the Swift community**
 
-If this skill helps improve your code reviews, please ⭐️ star the repository!
-```
+If this skill helps your code reviews, please star the repository!
+
+- [Issues](https://github.com/Viniciuscarvalho/swift-code-reviewer-skill/issues) | [Discussions](https://github.com/Viniciuscarvalho/swift-code-reviewer-skill/discussions)

package/SKILL.md

@@ -30,6 +30,7 @@ Use this skill when you need to:
 - Provide structured feedback to team members
 
 **Trigger patterns:**
+
 - "Review this PR"
 - "Review [filename].swift"
 - "Review my changes"
@@ -69,6 +70,7 @@ The skill follows a **four-phase workflow** to ensure comprehensive and actionab
 Execute checks across **six core categories**:
 
 #### 1. Swift Best Practices
+
 Reference: `swift-best-practices` skill knowledge base
 
 - **Concurrency Safety**
@@ -91,6 +93,7 @@ Reference: `swift-best-practices` skill knowledge base
   - Proper use of optionals
 
 #### 2. SwiftUI Quality
+
 Reference: `swiftui-expert-skill` knowledge base
 
 - **State Management**
@@ -118,6 +121,7 @@ Reference: `swiftui-expert-skill` knowledge base
   - Keyboard navigation
 
 #### 3. Performance
+
 Reference: `swiftui-performance-audit` knowledge base
 
 - **View Optimization**
@@ -256,7 +260,7 @@ Reference: `swiftui-performance-audit` knowledge base
    - Comparison with project guidelines
 
 3. **Provide Context**
-   - Explain *why* something is an issue
+   - Explain _why_ something is an issue
    - Reference best practices or standards
    - Suggest specific fixes with examples
    - Link to learning resources
@@ -266,6 +270,7 @@ Reference: `swiftui-performance-audit` knowledge base
 ### 1. Swift Language Quality
 
 **What to Check:**
+
 - Concurrency patterns (actors, async/await, Sendable)
 - Error handling (typed throws, Result type)
 - Optionals handling (avoid force unwrapping)
@@ -279,6 +284,7 @@ Reference: `swiftui-performance-audit` knowledge base
 ### 2. SwiftUI Patterns
 
 **What to Check:**
+
 - Property wrapper selection and usage
 - State management patterns
 - View lifecycle understanding
@@ -292,6 +298,7 @@ Reference: `swiftui-performance-audit` knowledge base
 ### 3. Performance Optimization
 
 **What to Check:**
+
 - View update optimization
 - ForEach identity and performance
 - Heavy work in view body
@@ -305,6 +312,7 @@ Reference: `swiftui-performance-audit` knowledge base
 ### 4. Security & Safety
 
 **What to Check:**
+
 - Force unwrap detection (`!`, `as!`, `try!`)
 - Input validation and sanitization
 - Sensitive data handling (passwords, tokens)
@@ -318,6 +326,7 @@ Reference: `swiftui-performance-audit` knowledge base
 ### 5. Architecture & Design
 
 **What to Check:**
+
 - MVVM, MVI, TCA, or other architecture compliance
 - Dependency injection patterns
 - Separation of concerns
@@ -331,6 +340,7 @@ Reference: `swiftui-performance-audit` knowledge base
 ### 6. Project-Specific Standards
 
 **What to Check:**
+
 - `.claude/CLAUDE.md` compliance
 - Custom architecture patterns
 - Design system usage
@@ -345,9 +355,11 @@ Reference: `swiftui-performance-audit` knowledge base
 This skill **references** (not duplicates) three foundational skills for domain expertise:
 
 ### 1. swift-best-practices
+
 **When to Use:** Reviewing Swift language usage, concurrency patterns, API design, or Swift 6+ migration
 
 **What it Provides:**
+
 - Swift 6+ concurrency patterns (actors, async/await, Sendable)
 - API design guidelines compliance
 - Availability pattern validation
@@ -355,14 +367,17 @@ This skill **references** (not duplicates) three foundational skills for domain
 - Modern Swift feature adoption
 
 **How to Leverage:**
+
 - Read `~/.claude/skills/swift-best-practices/references/concurrency.md` for concurrency checks
 - Reference `swift6-features.md` for Swift 6 migration patterns
 - Use `api-design.md` for naming and parameter validation
 
 ### 2. swiftui-expert-skill
+
 **When to Use:** Reviewing SwiftUI views, state management, or UI code
 
 **What it Provides:**
+
 - State management patterns (@Observable, @State, @Binding)
 - Modern SwiftUI API guidance (iOS 17+, macOS 14+)
 - View composition best practices
@@ -370,14 +385,17 @@ This skill **references** (not duplicates) three foundational skills for domain
 - Accessibility patterns
 
 **How to Leverage:**
+
 - Read `~/.claude/skills/swiftui-expert-skill/references/state-management.md` for property wrapper checks
 - Reference `modern-apis.md` for deprecation detection
 - Use `view-composition.md` for component structure validation
 
 ### 3. swiftui-performance-audit
+
 **When to Use:** Performance concerns identified or mentioned in PR description
 
 **What it Provides:**
+
 - View update optimization patterns
 - ForEach performance analysis
 - Layout thrash detection
@@ -385,14 +403,17 @@ This skill **references** (not duplicates) three foundational skills for domain
 - Memory management
 
 **How to Leverage:**
+
 - Read `~/.claude/skills/swiftui-performance-audit/SKILL.md` for performance audit workflow
 - Reference performance-specific checks when reviewing view code
 - Apply recommendations from the skill to performance-sensitive paths
 
 ### 4. swiftui-ui-patterns
+
 **When to Use:** Reviewing navigation architecture, sheet/modal routing, TabView setup, theming, async state management, focus handling, or API client patterns
 
 **What it Provides:**
+
 - Navigation architecture (route enums, RouterPath, centralized navigationDestination)
 - Sheet/modal routing (item-driven sheets, SheetDestination enum)
 - TabView with independent per-tab navigation history
@@ -402,11 +423,13 @@ This skill **references** (not duplicates) three foundational skills for domain
 - Lightweight API client pattern (closure-based structs, `.live()` / `.mock()` factories)
 
 **How to Leverage:**
+
 - Read `~/.claude/skills/swiftui-ui-patterns/references/navigation.md` for route enum and RouterPath checks
 - Reference `sheets-modals.md` for sheet routing validation
 - Use `theming.md` for semantic color enforcement
 
 **Integration Strategy:**
+
 1. Load relevant reference files from these skills as needed
 2. Apply their checklist items to the review
 3. Reference their documentation in feedback
@@ -415,6 +438,7 @@ This skill **references** (not duplicates) three foundational skills for domain
 ## Platform Support
 
 ### GitHub Pull Requests
+
 Use `gh` CLI for fetching PR data:
 
 ```bash
@@ -432,6 +456,7 @@ gh pr view <PR-number> --json comments
 ```
 
 ### GitLab Merge Requests
+
 Use `glab` CLI for fetching MR data:
 
 ```bash
@@ -449,6 +474,7 @@ glab mr note list <MR-number>
 ```
 
 ### Local Git Changes
+
 For uncommitted changes or manual review:
 
 ```bash
@@ -469,10 +495,11 @@ git show <commit-hash>
 
 The review report follows this structure:
 
-```markdown
+````markdown
 # Code Review Report
 
 ## Summary
+
 - **Files Reviewed**: X
 - **Total Findings**: Y
 - **Critical**: 0
@@ -483,6 +510,7 @@ The review report follows this structure:
 - **Refactoring Suggestions**: 4
 
 ## Executive Summary
+
 [Brief overview of the changes and overall code quality]
 
 ---
@@ -492,6 +520,7 @@ The review report follows this structure:
 ### File: Sources/Features/Login/LoginView.swift
 
 #### ✅ Positive Feedback
+
 1. **Excellent State Management** (line 23)
    - Proper use of @Observable for view model
    - Clean separation of concerns
@@ -501,11 +530,13 @@ The review report follows this structure:
    - Proper async/await integration
 
 #### 🔴 Critical Issues
+
 1. **Data Race Risk** (line 67)
    - **Severity**: Critical
    - **Category**: Concurrency
    - **Issue**: Mutable state accessed from multiple actors without synchronization
    - **Fix**:
+
      ```swift
      // Before
      class LoginViewModel {
@@ -518,14 +549,17 @@ The review report follows this structure:
          @Published var isLoading = false
      }
      ```
+
    - **Reference**: swift-best-practices/references/concurrency.md
 
 #### 🟡 High Priority
+
 1. **Force Unwrap Detected** (line 89)
    - **Severity**: High
    - **Category**: Safety
    - **Issue**: Force unwrapping optional can cause crash
    - **Fix**:
+
      ```swift
      // Before
      let user = fetchUser()!
@@ -536,9 +570,11 @@ The review report follows this structure:
          return
      }
      ```
+
    - **Reference**: Project coding standard (.claude/CLAUDE.md:45)
 
 #### 💡 Refactoring Suggestions
+
 1. **Extract Subview** (lines 120-150)
    - Consider extracting login form into separate view
    - Improves testability and reusability
@@ -548,20 +584,24 @@ The review report follows this structure:
 ## Prioritized Action Items
 
 ### Must Fix (Critical/High)
+
 1. [ ] Fix data race in LoginViewModel.swift:67
 2. [ ] Remove force unwrap in LoginView.swift:89
 
 ### Should Fix (Medium)
+
 1. [ ] Add documentation to public APIs
 2. [ ] Improve error handling in NetworkService.swift
 
 ### Consider (Low)
+
 1. [ ] Refactor login form into separate view
 2. [ ] Add more unit tests for edge cases
 
 ---
 
 ## Positive Patterns Observed
+
 - Excellent use of @Observable for state management
 - Consistent adherence to project architecture (MVVM)
 - Comprehensive accessibility support
@@ -569,14 +609,16 @@ The review report follows this structure:
 - Good test coverage for core functionality
 
 ## References
+
 - [Swift Best Practices](~/.claude/skills/swift-best-practices/SKILL.md)
 - [SwiftUI Expert Guide](~/.claude/skills/swiftui-expert-skill/SKILL.md)
 - [Project Coding Standards](.claude/CLAUDE.md)
-```
+````
 
 ## How to Use
 
 ### Example 1: Review Specific File
+
 ```
 User: "Review UserProfileView.swift"
 
@@ -588,6 +630,7 @@ Steps:
 ```
 
 ### Example 2: Review Git Changes
+
 ```
 User: "Review my uncommitted changes"
 
@@ -600,6 +643,7 @@ Steps:
 ```
 
 ### Example 3: Review Pull Request
+
 ```
 User: "Review PR #123"
 
@@ -613,6 +657,7 @@ Steps:
 ```
 
 ### Example 4: Review Against Custom Guidelines
+
 ```
 User: "Review LoginViewModel.swift against our coding standards"
 
@@ -625,6 +670,7 @@ Steps:
 ```
 
 ### Example 5: Review Multiple Files
+
 ```
 User: "Review all ViewModels in the Features folder"
 
@@ -637,6 +683,7 @@ Steps:
 ```
 
 ### Example 6: Review Navigation / Routing Code
+
 ```
 User: "Review our navigation setup and routing code"
 
@@ -664,16 +711,19 @@ Steps:
 This skill includes the following reference materials:
 
 ### Core References
+
 - **review-workflow.md**: Detailed step-by-step review process, git commands, and diff parsing strategies
 - **feedback-templates.md**: Templates for positive/negative comments, severity classification guidelines
 
 ### Quality Checklists
+
 - **swift-quality-checklist.md**: Swift 6+ concurrency, error handling, optionals, access control, naming
 - **swiftui-review-checklist.md**: Property wrappers, state management, modern APIs, view composition
 - **performance-review.md**: View updates, ForEach optimization, layout efficiency, resource management
 - **security-checklist.md**: Input validation, sensitive data, keychain, network security
 
 ### Architecture & Customization
+
 - **architecture-patterns.md**: MVVM, MVI, TCA patterns, dependency injection, testing strategies
 - **custom-guidelines.md**: How to read and parse .claude/CLAUDE.md and project-specific standards
 
@@ -692,7 +742,7 @@ This skill includes the following reference materials:
 3. **Be Specific and Actionable**
    - Include exact file:line references
    - Provide code examples for fixes
-   - Explain *why* something is an issue
+   - Explain _why_ something is an issue
    - Link to relevant documentation
 
 4. **Prioritize by Severity**
@@ -725,6 +775,6 @@ For runtime analysis, recommend using Instruments or other profiling tools.
 
 ## Version
 
-**Version**: 1.1.0
+**Version**: 1.1.1
 **Last Updated**: 2026-03-16
 **Compatible with**: Swift 6+, SwiftUI (iOS 17+, macOS 14+, watchOS 10+, tvOS 17+, visionOS 1+)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "swift-code-reviewer-skill",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "Claude Code skill for comprehensive Swift/SwiftUI code reviews with multi-layer analysis",
   "keywords": [
     "claude",