swiftlint

What This Skill Does

The SwiftLint skill enables OpenClaw to enforce clean, maintainable Swift code by integrating static analysis directly into your development workflow. It identifies stylistic errors, potential bugs, and code smells by checking your source code against established community conventions (or your custom project rules). Beyond simple reporting, this tool can automatically fix common violations, saving developers significant time during code reviews and cleanup phases.

Installation

To enable this functionality, use the command: clawhub install openclaw/skills/skills/alexissan/swiftlint. Ensure you have the SwiftLint CLI installed on your machine. You can install it via Homebrew (brew install swiftlint), Mint, or by adding it as a Swift Package Manager plugin in your Package.swift file. Once installed, ensure the swiftlint executable is available in your system path.

Use Cases

This skill is perfect for maintaining consistency across large-scale Swift projects or ensuring that code contributed by multiple team members adheres to a singular style guide. Use it to scan entire repositories to identify legacy code that violates current standards, or target specific files to ensure high-quality code during the commit process. It is especially powerful when configured for Continuous Integration (CI) pipelines, where you can export results into formats like JUnit, JSON, or Checkstyle to automatically fail builds that contain stylistic regressions.

Example Prompts

1. "Check my code style in the current directory and list any major violations."
2. "I see a lot of SwiftLint warnings in the 'Sources/' folder; please autocorrect all fixable issues."
3. "Run a lint check on 'ViewModel.swift' and provide the output in JSON format so I can analyze it programmatically."

Tips & Limitations

Always run a linting check before performing an autocorrection to review what is being modified. Note that not all SwiftLint violations are automatically fixable; some logic-heavy or complex stylistic issues require manual intervention. For projects with strict requirements, consider creating a .swiftlint.yml file in your root directory to customize which rules are enforced. Be aware that running --fix modifies your files directly; ensure your work is committed to version control before executing these commands to prevent unexpected data loss.