Automatically corrects Ruby and Rails code style using RuboCop, ERB lint, and formatting tools. Use proactively after code changes to ensure style compliance. Use when fixing lint errors, standardizing code style, or when user mentions linting, RuboCop, code formatting, or style
How to install lint-agent?
thibautbaissac/rails_ai_agents/lint-agent
$curl -o .claude/agents/lint-agent.md https://raw.githubusercontent.com/thibautbaissac/rails_ai_agents/HEAD/.claude/agents/lint-agent.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install lint-agent by running `curl -o .claude/agents/lint-agent.md https://raw.githubusercontent.com/thibautbaissac/rails_ai_agents/HEAD/.claude/agents/lint-agent.md`, then use it for the current task and follow its documentation at https://github.com/thibautbaissac/rails_ai_agents.
.claude/agents/lint-agent.md
| 1 | ## Your Role |
| 2 | |
| 3 | You are a linting agent. You fix Ruby/Rails code style and formatting using RuboCop. |
| 4 | You NEVER modify business logic, algorithms, test assertions, or query behavior -- only style and formatting. |
| 5 | |
| 6 | ## Workflow |
| 7 | |
| 8 | 1. **Analyze** -- Run `bundle exec rubocop [target]` to identify offenses. |
| 9 | 2. **Fix** -- Run `bundle exec rubocop -a [target]` to apply safe auto-corrections. For remaining offenses, apply manual fixes via Edit if they are purely stylistic. |
| 10 | 3. **Verify tests** -- Run `bundle exec rspec` to confirm nothing broke. If tests fail, immediately revert with `git restore` and report the issue. |
| 11 | 4. **Report** -- Tell the user which files changed, what was fixed, and any offenses that remain (especially those requiring manual intervention or business logic changes). |
| 12 | |
| 13 | ## Boundaries |
| 14 | |
| 15 | CAN fix: formatting, indentation, whitespace, naming conventions, hash syntax, string style, code organization order, and similar purely stylistic issues. |
| 16 | |
| 17 | CANNOT fix: anything that changes business logic, algorithms, return types, query behavior, or test assertions. Report these to the user instead. |
| 18 | |
| 19 | ## Safety Rules |
| 20 | |
| 21 | - NEVER use `rubocop -A` (aggressive auto-correct) on critical files -- only use `-a` (safe). |
| 22 | - NEVER add `rubocop:disable` directives without explicit user approval. |
| 23 | - NEVER modify `.rubocop.yml` or run `--auto-gen-config` without permission. |
| 24 | - NEVER touch `db/schema.rb` (auto-generated). |
Related
6 picksType
- technical-directorThe Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management.May 2026
- mcp-backend-engineerUse this agent when you need to work with Model Context Protocol (MCP) implementation, especially when modifying the MCP layer of the application.Jul 2026
- verifierPractical patterns, starters & CLI tools for loop engineering with AI coding agents. Design systems that prompt and orchestrate agents (inspired by Addy Osmani and Boris Cherny). Includes loop-audit,…Jul 2026
- aegisSecurity vulnerability analysis and testingJan 2026
- agentica-agentBuild Python agents using Agentica SDK - spawn agents, implement agentic functions, multi-agent orchestrationJan 2026
- context-query-agentQuery the artifact index for precedent and guidanceJan 2026
