lint-validator

Lint changed Swift files with SwiftLint and report violations.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/tanujsutaria/VitalArc --skill lint-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lint-validator
Source: https://github.com/tanujsutaria/VitalArc/tree/main/.claude/skills/lint-validator
Command: npx skills add https://github.com/tanujsutaria/VitalArc --skill lint-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lint changed Swift files and report violations to enforce code quality and prevent defects from entering the codebase.

Core Features & Use Cases

  • Scope-limited linting: Checks only changed files (staged and unstaged vs HEAD) to keep feedback fast.
  • Non-intrusive reporting: Reports violations without auto-fixing by default.
  • Pre-commit and review integration: Serves as a quality gate before commits or during code reviews.

Quick Start

Run the lint-validator on changed files to detect SwiftLint violations. By default, it lints only changed files; use --all to lint all files, --fix to auto-fix, and --strict to treat warnings as errors.

Frequently Asked Questions about lint-validator

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

FAQPage Schema
How do I lint only changed Swift files before a commit?

Yes, you can auto-fix SwiftLint violations by using the --fix flag. By default, the linter provides non-intrusive reporting without modifying files, but passing --fix allows it to automatically correct issues in changed Swift files.

What do I need to run SwiftLint in a Bash pre-commit hook?

To treat SwiftLint warnings as errors, use the --strict flag. This enforces stricter code quality gates during pre-commit or code review workflows, preventing commits when any warning-level violations are detected in changed Swift files.

Can I lint all Swift files instead of just the changed ones?

Yes, you can lint all Swift files by using the --all flag. While the default behavior checks only staged and unstaged changes versus HEAD to keep feedback fast, --all expands the scope to the entire codebase.

Why use scope-limited SwiftLint checks during code reviews?

Scope-limited linting speeds up code reviews by running SwiftLint exclusively on changed files identified via git diff HEAD. This targets quality gates at new changes, preventing defects without slowing down the process with full-codebase scans.