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.
73
91%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
SKILL.mdrails-bug-triage/
- name:
- rails-bug-triage
- description:
- Use when investigating a bug in a Ruby on Rails codebase and you need to turn the report into a reproducible failing spec and fix plan. Covers reproduction, scope narrowing, boundary selection, and TDD-first handoff.
Rails Bug Triage
Use this skill when a bug report exists but the right reproduction path and fix sequence are not yet clear.
Core principle: Do not guess at fixes. Reproduce the bug, choose the right failing spec, then plan the smallest safe repair.
Quick Reference
| Step | Goal |
|---|---|
| Reproduce | Confirm the bug is real and current |
| Localize | Find the layer where the failure is observed |
| Choose spec | Pick the highest-value failing spec |
| Plan fix | Define the smallest repair path |
HARD-GATE
DO NOT propose a fix before the bug is reproduced or a failing spec is identified.
DO NOT accept "it probably lives in X" as evidence.
ALWAYS hand off to a failing spec before implementation begins.When to Use
- The user reports a bug and wants help investigating it.
- A failing behavior is described, but the responsible Rails layer is unknown.
- You need to convert a bug report into a TDD-ready fix plan.
- Next step: Chain to
rails-tdd-slicesto choose the first spec, thenrspec-best-practicesand the implementation skill for the affected area.
Process
- Capture the report: Restate the expected behavior, actual behavior, and reproduction steps.
- Bound the scope: Identify whether the issue appears in request handling, domain logic, jobs, engine integration, or an external dependency.
- Gather current evidence: Logs, error messages, edge-case inputs, recent changes, or missing guards.
- Choose the first failing spec: Pick the boundary where the bug is visible to users or operators.
- Define the smallest fix path: Name the likely files and the narrowest behavior change that should make the spec pass.
- Hand off: Continue through
rails-tdd-slices->rspec-best-practices-> implementation skill.
Triage Output
Return findings in this shape:
- Observed behavior
- Expected behavior
- Likely boundary
- First failing spec to add
- Smallest safe fix path
- Follow-up skills
Boundary Guide
| Bug shape | Likely first spec |
|---|---|
| Wrong status code, params handling, JSON payload | Request spec |
| Invalid state transition, validation, calculation | Model or service spec |
| Async side effect missing or duplicated | Job spec |
| Engine routing/install/generator regression | Engine spec |
| Third-party mapping/parsing issue | Integration or client-layer spec |
Common Mistakes
| Mistake | Reality |
|---|---|
| Jumping straight to the suspected fix | Suspicion is not proof; reproduce first |
| Using a unit spec when the bug is visible at request level | Start where the failure is actually observed |
| Bundling reproduction, refactor, and new features together | Fix the bug in the smallest safe slice |
| Treating flaky evidence as a green light to patch blindly | Stabilize reproduction before changing code |
Red Flags
- No one can state exact expected vs actual behavior
- The first spec does not reproduce the reported issue
- The proposed fix touches unrelated layers immediately
- The explanation relies on "probably", "maybe", or "should"
Integration
| Skill | When to chain |
|---|---|
| rails-tdd-slices | To choose the strongest first failing spec for the bug |
| rspec-best-practices | To run the TDD loop correctly after the spec is chosen |
| refactor-safely | When the bug sits inside a risky refactor area and behavior must be preserved first |
| rails-code-review | To review the final bug fix for regressions and missing coverage |
| rails-architecture-review | When the bug points to a deeper boundary or orchestration problem |
api-rest-collection
create-prd
ddd-boundaries-review
ddd-rails-modeling
ddd-ubiquitous-language
generate-tasks
rails-agent-skills
rails-architecture-review
rails-background-jobs
rails-bug-triage
rails-code-conventions
rails-code-review
rails-engine-compatibility
rails-engine-docs
rails-engine-extraction
rails-engine-installers
rails-engine-release
rails-engine-reviewer
rails-engine-testing
rails-graphql-best-practices
rails-migration-safety
rails-review-response
rails-security-review
rails-stack-conventions
rails-tdd-slices
refactor-safely
rspec-best-practices
rspec-service-testing
ruby-api-client-integration
ruby-service-objects
strategy-factory-null-calculator
ticket-planning
yard-documentation