CtrlK
BlogDocsLog inGet started
Tessl Logo

igmarin/rails-agent-skills

Curated library of 28 atomic skills and 9 personas for Ruby on Rails development. Organized by category: testing, code-quality, engines, infrastructure, api, context, and personas. Covers code review, architecture, security, testing (RSpec), engines, Hotwire, and TDD automation. Shared Ruby skills (YARD docs, DDD, service objects) have moved to ruby-core-skills.

93

1.16x
Quality

95%

Does it follow best practices?

Impact

93%

1.16x

Average score across 28 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

task.mdevals/scenario-20/

Test Service Task

Problem

A Rails team needs help with a task in this area:

Use when writing RSpec tests for service objects in spec/services/ — write spec FIRST and verify it fails for the right reason, use subject(:service_call) { described_class.call(params) } with describe '.call', test the public contract not internal implementation, use instance_double for isolation and create for integration, cover happy path + error/edge cases + blank/invalid input, use aggregate_failures for multi-assertion tests, change matchers for state verification, travel_to for time-dependent logic, FactoryBot hash factories (class: Hash with initialize_with) for API responses.

The team has asked for a concise implementation artifact that a reviewer can inspect without needing to observe the agent's process.

Output

Create answer.md with:

  • a short plan for the work
  • the concrete Rails-oriented artifact or recommendation
  • the verification steps or quality gates that should be run
  • any assumptions that affect the result

README.md

tile.json