Rails

What This Skill Does

The Rails skill acts as a specialized architectural advisor for Ruby on Rails development within the OpenClaw ecosystem. It provides expert guidance on writing idiomatic, performant, and secure Rails applications. By focusing on common pitfalls—such as the infamous N+1 query problem, excessive use of Active Record callbacks, and memory-intensive data processing—this skill ensures that your codebase remains maintainable and scalable. It functions as a linting and architectural companion that helps you navigate complex Rails patterns, including controller filtering, nested routing, and secure job processing with ActiveJob.

Installation

To integrate this skill into your environment, run the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/rails

Use Cases

• Code Review: Automatically identify potential performance bottlenecks like memory-heavy all.each iterations or missing database indexes.
• Security Audits: Detect vulnerabilities related to mass assignment, improper strong parameter implementation, or potential SQL injection vectors.
• Refactoring Support: Transform legacy code by replacing convoluted before_action chains or misplaced business logic inside controllers with cleaner Service Objects or concerns.
• Troubleshooting: Debug subtle issues such as silent callback failures, orphan database records caused by missing dependent: :destroy associations, and render/redirect flow control bugs.

Example Prompts

1. "I'm experiencing an N+1 query issue in my user dashboard. Can you analyze my controller and query logic to suggest the proper includes or eager_load implementation?"
2. "Review my model file. I'm using a default_scope to filter active records, but it's causing issues with my join queries. How should I refactor this?"
3. "Help me secure this controller action. I need to make sure my strong parameters are correctly configured and that I'm not exposing sensitive attributes."

Tips & Limitations

• Memory Management: Always prioritize find_each over all.each to keep memory consumption predictable, especially for background tasks.
• Execution Flow: Remember that redirect_to and render do not implicitly stop controller execution. Always use and return or an explicit return statement to prevent double-render errors.
• Callback Awareness: Avoid overusing callbacks for complex logic. Business logic should ideally reside in Service Objects, as callbacks can make debugging difficult and often cause side effects in test suites.
• Constraint: This skill provides architectural advice and code snippets but requires manual verification for production deployment.