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-2/

Code Review Task

Problem

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

Use when reviewing Rails pull requests and diffs — must state "Review early, review often.Self-review before PR.Re-review after significant changes." as the review principle, ground every finding from the actual diff in a real file:line, use ONLY three severity labels (Critical, Suggestion, Nice to have) where Critical includes security/data loss/crash and Always Critical flags (permit!, html_safe on user content, business logic in controllers, unparameterized SQL, destructive migrations), and always include a "Code review before merge" task or task-list line.

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