ruby-ecosystem

Use this agent when working with Ruby code in any context—whether pure Ruby, Rails applications, CLI tools, or gems. Invoke this agent for: - **Implementation work**: New features, refactoring, bug fixes, or architectural improvements - **Quality assurance**: Code review, ensuring RuboCop compliance, running RSpec/Capybara tests, coverage analysis with SimpleCov - **Security audits**: Running bundler-audit and Brakeman (for Rails apps) to identify vulnerabilities - **Documentation sync**: Ensuring YARD documentation in `docs/` accurately reflects current implementation - **Best practices enforcement**: Applying idiomatic Ruby patterns, Simple Design Heuristics, and functional core/imperative shell architecture - **Test-driven development**: Writing specs that reveal intent and test behavior, not implementation - **Final review**: Before any commit, ensuring all quality gates pass (tests green, linting clean, security clear, docs current) Examples: <example> Context: User has just written a new service object for processing payments in a Rails application. user: "I've created a PaymentProcessor service. Here's the code: [code snippet]" assistant: "Let me use the ruby-craftsperson agent to review this service for code quality, test coverage, RuboCop compliance, and ensure it follows our functional core/imperative shell principles." <Task tool invocation to ruby-craftsperson> </example> <example> Context: User is about to commit changes to a Ruby gem. user: "I think I'm ready to commit these changes to the User model." assistant: "Before committing, I'll invoke the ruby-craftsperson agent to run the full quality gate check: RSpec tests, RuboCop linting, SimpleCov coverage, bundler-audit security scan, and verify YARD docs are synchronized." <Task tool invocation to ruby-craftsperson> </example> <example> Context: User wants to add a new feature to extract user data. user: "I need to add a feature that exports user data to CSV format." assistant: "I'll use the ruby-craftsperson agent to implement this feature following TDD principles, ensuring we write the spec first, then implement using idiomatic Ruby with proper separation of concerns." <Task tool invocation to ruby-craftsperson> </example> <example> Context: Agent proactively notices code that could be improved after user makes a change. user: "I've updated the authentication logic in the sessions controller." assistant: "I notice you've made changes to authentication. Let me invoke the ruby-craftsperson agent to review for security best practices, ensure Brakeman is happy, and verify the integration tests cover the authentication flow properly." <Task tool invocation to ruby-craftsperson> </example>