CtrlK
BlogDocsLog inGet started
Tessl Logo

igmarin/rails-agent-skills

Curated library of AI agent skills for Ruby on Rails development. Covers code review, architecture, security, testing (RSpec), engines, service objects, DDD patterns, and workflow automation.

98

1.38x
Quality

99%

Does it follow best practices?

Impact

98%

1.38x

Average score across 26 eval scenarios

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

BOUNDARY_GUIDE.mdrails-bug-triage/

Bug Triage Boundary Guide

Maps common bug shapes to the highest-value first failing spec.

Bug shapeLikely first specPath
Wrong status code, params handling, JSON payloadRequest specspec/requests/
Invalid state transition, validation, calculationModel or service specspec/models/ or spec/services/
Async side effect missing or duplicatedJob specspec/jobs/
Engine routing/install/generator regressionEngine specDummy app path
Third-party mapping/parsing issueIntegration or client-layer specspec/services/module_name/

Diagnosing the Right Layer

  • HTTP symptoms (wrong status, wrong JSON shape, redirect loops): start at request level
  • Data symptoms (wrong value saved, wrong validation message): start at model or service
  • Timing symptoms (missing email, job not enqueued): start at job or service spec
  • Engine symptoms (routes not found, generator broke): use dummy app request spec

When the Boundary Is Unclear

  1. Write the spec at the highest visible symptom boundary first.
  2. Run it — if it fails for the wrong reason (e.g., factory error), move down a layer.
  3. The correct boundary is where the failure message directly names the missing behavior.

README.md

tile.json