reviewing-code-changes

Audit Swift/SwiftUI code changes for architecture and styling violations.

2|1|Updated Apr 13, 2025
One-click install
npx skills add https://github.com/Jose-Luis-Nunez/FitnessApp --skill reviewing-code-changes-jose-luis-nunez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-code-changes
Source: https://github.com/Jose-Luis-Nunez/FitnessApp/tree/main/.cursor/skills/reviewing-code-changes
Command: npx skills add https://github.com/Jose-Luis-Nunez/FitnessApp --skill reviewing-code-changes-jose-luis-nunez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Swift/SwiftUI code changes frequently introduce architecture violations, hardcoded styling, dead code, or missed reuse. This skill guides reviewers to validate changes and maintain code health during and after refactoring.

Core Features & Use Cases

  • Architecture compliance checks, AppStyle consistency, and referential integrity.
  • Detection of hardcoded styling, dead code, and anti-patterns; ensures reuse and maintainability.
  • Use when the user asks to review code, audit styling, verify architecture, or clean up after refactoring.

Quick Start

Review the git-diff of changed Swift/SwiftUI files and return a structured violation report with line numbers and suggested fixes.

Frequently Asked Questions about reviewing-code-changes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Swift and SwiftUI code changes for architecture violations?

To audit Swift code changes, analyze the git diff to detect architecture violations, styling inconsistencies, dead code, and referential integrity issues, returning a structured report with line numbers and suggested fixes.

What is the best way to check SwiftUI styling consistency after refactoring?

Check SwiftUI styling consistency by auditing code changes against AppStyle tokens and shared components, identifying hardcoded styling and providing clear fixes with line references to ensure maintainability.

How do I detect dead code and anti-patterns in a Swift diff?

Detect Swift dead code and anti-patterns by performing category checks on the changed files during refactoring or large multi-file edits, ensuring component reuse and verifying referential integrity.

When should I run a code review audit on my Swift project?

Run a code review audit during refactoring, after large multi-file edits, or when requested to verify architecture compliance, audit styling, and clean up code health in your Swift/SwiftUI projects.

How do I verify referential integrity in SwiftUI multi-file edits?

Verify SwiftUI referential integrity by analyzing the diff of changed files to ensure all references remain intact and valid, detecting missed reuse opportunities and anti-patterns introduced during the edit.

Does this code review process work with standard git diff output?

Yes, the code review process works by reviewing the standard git diff of changed Swift/SwiftUI files to generate a structured violation report containing line numbers, suggested fixes, and architecture compliance checks.