Rails Lint

Rails Lint

Run the project's configured quality checks, fix violations without changing behavior, and verify the final diff.

Workflow

1. Inspect Project Configuration

Use the project command and configuration for the requested check. Relevant sources can include:

• .rubocop.yml
• .rubocop_todo.yml
• .erb-lint.yml
• Gemfile
• bin/ci or the relevant CI workflow

Use project-provided commands when they differ from the defaults below. Do not replace local conventions with generic style preferences.

2. Scope The Check

# Unstaged changes
git diff --name-only

# Staged changes
git diff --cached --name-only

For a small change, use checks scoped to affected files. Run full checks when the user requests a repository audit, the configuration change affects the repository, or project rules require them.

3. Run Checks

RuboCop:

# Full check
bundle exec rubocop

# Focused file or directory
bundle exec rubocop app/models/user.rb

# Specific cop
bundle exec rubocop --only Style/StringLiterals

ERB Lint:

bundle exec erblint --lint-all

Brakeman:

bin/brakeman --no-pager

If a tool is not configured in the project, report that instead of adding it without approval.

4. Apply Corrections

Use safe automatic corrections on the requested files. These commands apply to the full repository, so use them only for that scope:

bundle exec rubocop -a
bundle exec erblint --lint-all --autocorrect

Inspect the resulting diff. Use RuboCop's unsafe correction mode only when every semantic change will be reviewed:

bundle exec rubocop -A

Do not run -A by default. Do not mix unrelated formatting changes into the requested work.

5. Resolve Remaining Violations

Read the cop documentation before making non-obvious manual changes:

bundle exec rubocop --show-cops Style/StringLiterals

Follow these rules:

• Fix the code when the cop identifies a real issue.
• Respect project configuration when style choices are intentional.
• Use inline disables only for a justified exception, with the narrowest possible scope.
• Do not generate or expand .rubocop_todo.yml unless the user explicitly requests a baseline.
• Do not change public behavior merely to satisfy a metric cop.

Common fixes:

6. Verify

Rerun checks affected by corrections and inspect the final diff. Stop when the requested scope passes. Report pre-existing failures and unavailable tools separately; do not expand the work to unrelated violations.

Do not stage or commit automatically.

Output

Report:

1. Checks run and their results
2. Automatic corrections applied
3. Manual fixes with cop names and file locations
4. Remaining warnings or unavailable tools
5. Final pass or needs-attention verdict