lint-patterns

Apply RuboCop safe corrections to Ruby on Rails files and directories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you safely clean up Ruby on Rails code style and lint violations without accidentally changing behavior or breaking database interactions.

Core Features & Use Cases

  • RuboCop command guidance: Run analysis, inspect offenses, and apply safe auto-corrections tailored to projects, directories, files, or tests.
  • Safe vs unsafe correction guardrails: Define a “safe zone” for formatting, naming, quotes, modern hash syntax, and organization, while explicitly prohibiting risky business-logic and query transformations.
  • Rails Omakase standards: Enforce consistent conventions like indentation, line length, quote style, hash syntax, and typical model/controller structure.
  • Workflow for verification: Re-run RuboCop after changes and run tests, including clear recovery instructions if failures occur.

Quick Start

Run bundle exec rubocop -a on the specific file or directory you want to lint, then re-run bundle exec rubocop to confirm only safe fixes were applied.

Frequently Asked Questions about lint-patterns

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

FAQPage Schema
How do I safely auto-correct Rails lint issues without changing business logic?

Run bundle exec rubocop -a on specific files or directories to apply safe auto-corrections for formatting and style. This enforces Rails Omakase conventions while explicitly avoiding risky business-logic and query transformations.

What is the difference between safe and unsafe RuboCop corrections in Ruby on Rails?

Safe corrections cover formatting, naming, quotes, modern hash syntax, and organization. Unsafe corrections involve risky business-logic and query transformations that are explicitly prohibited to prevent changing application behavior.

How do I verify RuboCop auto-corrections did not break my Rails tests?

After applying auto-corrections, re-run bundle exec rubocop to confirm only safe fixes were applied, then execute Rails tests to verify behavior is unchanged. Clear recovery instructions are provided if test failures occur.

Can I use RuboCop to enforce Rails Omakase style conventions on specific directories?

Yes, RuboCop can target specific files, directories, or tests in your Rails project to apply Omakase conventions like indentation, line length, quote style, and hash syntax consistently across the targeted scope.

What should I do if RuboCop auto-correction breaks my Rails application?

If RuboCop auto-correction causes failures, review the changes against the safe vs danger zone rules. Revert the unsafe modifications, ensure you are only using the -a flag for safe autocorrect, and re-run Rails tests.