lint_skill

Overview

This skill runs linting and code quality checks for Ruby and ERB files and performs security scans when needed. It automates selection of the right tools, supports auto-fixing where available, and produces actionable results ready for commit. Use it as a pre-push step to catch style, syntax, and common security issues early.

How this skill works

The skill inspects changed files and decides which checks to run: Ruby, ERB, or security scans. It executes standardrb for Ruby, erblint for ERB, and Brakeman for security, optionally invoking auto-fix commands when requested. Outputs are parsed to extract errors, warnings, and suggested fixes, and fixes can be committed with the message prefix style: linting.

When to use it

• Before pushing code to origin to prevent style regressions
• After modifying Ruby (.rb) files to enforce project standards
• After editing ERB templates to catch template-specific issues
• When performing a security check on Rails code paths
• As part of a pre-merge check or CI local run

Best practices

• Run the skill against only changed files to save time and noise
• Prefer auto-fix flags (--fix or --autocorrect) for straightforward style issues
• Review parsed output to prioritize fixes that affect functionality or security
• Commit automated fixes with a clear prefix like style: linting
• Keep tool dependencies (bundler, gems) up to date to match project config

Example use cases

• A developer edits controllers and views; run the skill to auto-fix style and detect ERB template problems before opening a PR
• Integrate the skill in a local pre-push hook to run fast lint checks and a security scan on demand
• Run a full scan before a release: standardrb for code style, erblint for templates, and Brakeman for vulnerabilities
• Use the autocorrect flags to batch-apply formatting fixes, then commit with the style: linting message