What problem does it solve? When just format-check fails — locally, in a pre-commit hook, or in CI — it is tempting to silence the failure with a SwiftLint baseline, a // swiftlint:disable comment, or a threshold bump. This Skill enforces the project's rule that every violation is fixed in source code, and guides you through fixing swift-format and SwiftLint violations correctly. ## Core Features & Use Cases - Two-gate diagnosis: Separates mechanical swift-format layout failures (fixed with just format) from semantic swiftlint lint --strict violations that require real code changes. - Fix-in-source guidance: Maps common rules (force_unwrapping, file_length, cyclomatic_complexity, identifier_name, and more) to design-level fixes aligned with guides/CODE_GUIDE.md and Apple's API Design Guidelines. - Anti-laundering guardrails: Explicitly forbids baselines, threshold bumps, and unjustified disable comments, with red-flag checks before and after fixing. - Use Case: A PR's CI format-check job fails with three SwiftLint violations. Use this Skill to reproduce locally, fix each violation in source, run the @code-review agent on the changed files, and verify a clean just format-check before committing. ## Quick Start Ask the AI to fix the failing just format-check output by applying this skill and repairing each SwiftLint violation in source code.
