swiftlint

Enforce Swift style and convention compliance via configurable lint rules.

Updated May 10, 2026
One-click install
npx skills add https://github.com/FelixRauch/medat-figuren --skill swiftlint-felixrauch
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: swiftlint
Source: https://github.com/FelixRauch/medat-figuren/tree/main/.agents/skills/swiftlint
Command: npx skills add https://github.com/FelixRauch/medat-figuren --skill swiftlint-felixrauch

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve?

SwiftLint helps teams automatically detect and prevent inconsistent Swift style and risky patterns early, reducing manual review overhead and keeping codebases uniform over time.

Core Features & Use Cases

  • Rules & Configuration: Define lint behavior via .swiftlint.yml, including disabled_rules, opt_in_rules, only_rules, severity tuning, and scoped included/excluded paths.
  • Suppression & Baselines: Handle legacy violations safely using targeted swiftlint:disable comments and baseline files for incremental rollout.
  • Multiple Integrations: Choose between a SwiftPM build tool plugin, command plugin, Xcode run script phases, and CI reporter formats (including SARIF) for enforcement at scale.

Quick Start

Use SwiftLint with the build tool plugin (SimplyDanny/SwiftLintPlugins) and create a .swiftlint.yml configuration at the project root to start enforcing rules during builds and in CI.

Frequently Asked Questions about swiftlint

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

FAQPage Schema
How do I enforce consistent Swift code style in CI and local development?β–Ό

You can enforce consistent Swift code style by applying a configurable lint rule set to Swift source code via a root `.swiftlint.yml` file, integrating checks through SwiftPM build tool plugins or CLI runners with structured reporter output for automated CI checks and local builds.

What is the best way to incrementally adopt Swift static analysis on an existing codebase?β–Ό

Incremental adoption of Swift static analysis is managed safely using baseline files and targeted `swiftlint:disable` suppression comments, allowing you to handle legacy violations without fixing the entire codebase at once during rollout.

Can I configure specific Swift lint rules and severity levels for different project paths?β–Ό

Yes, you can configure specific Swift lint rules and severity levels by defining `disabled_rules`, `opt_in_rules`, and `only_rules` in the `.swiftlint.yml` file, while scoping enforcement to specific directories using `included` and `excluded` paths.

Does SwiftLint work with SwiftPM packages and Xcode projects?β–Ό

SwiftLint works with both SwiftPM packages and Xcode projects, supporting integration through SwiftPM build tool plugins, command plugins, and Xcode run script phases to provide deterministic linting across different development environments.

How do I generate structured CI reports for Swift lint violations?β–Ό

You can generate structured CI reports for Swift lint violations by running the linter through CLI runners or build tool plugins that support structured reporter formats, including SARIF, for enforcement and tracking at scale.