igmarin/rails-skills-orchestrator
skills/orchestration/rails-skills-orchestrator/SKILL.md
Triages and decomposes complex Ruby on Rails requests into ordered sub-tasks, then delegates to specialized skills for testing, code review, engines, DDD, and patterns. Enforces TDD discipline across all code-producing work. Use when scope is unclear, the best approach is uncertain, or a request spans multiple Rails concerns. Trigger: where do I start, help me plan a Rails feature, break this down, what's the best approach for this Rails work, not sure how to approach this, multi-step Rails task, complex Rails task, what should I do first.
$ install --global
skillsauthnpx skillsauth add igmarin/rails-agent-skills rails-skills-orchestratorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 3:01 AM250.9s4 files scanned
SKILL.md
- name:
- rails-skills-orchestrator
- license:
- MIT
- description:
- >
- request spans multiple Rails concerns. Trigger:
- where do I start, help me plan a Rails feature,
- user-invocable:
- true
- version:
- 1.0.0
- keywords:
- rails, ruby, tdd, testing, code-review, engines, ddd, orchestration, entry-point
Rails Skills Orchestrator
Triages and decomposes any Ruby on Rails request into ordered sub-tasks, then delegates to the correct specialized skill. Enforces the Tests Gate Implementation mandate across all code-producing work.
When a task arrives, identify the matching skill from the tables below and name it explicitly as the next skill to use before responding further. Generated artifacts (YARD docs, Postman collections, READMEs) must be in English unless the user explicitly requests another language.
Invocation example:
User: "I want to add a payment feature but I'm not sure where to start."
Claude: "This is a feature request with unclear scope. I'll start by loading the codebase context, then create a PRD.\n\nNext skill: skills/context/rails-context-engineering"
CROSS-CUTTING MANDATE: Tests Gate Implementation
Non-negotiable: no implementation code until a test exists, runs, and fails for the right reason (feature missing, not config/syntax).
Core Skills (Most Common)
| Skill | Use when... | | ----- | ----------- | | rails-context-engineering | Before any code/spec/PRD in an existing Rails codebase — load schema, routes, nearest patterns, surface ambiguity | | rspec-best-practices | Writing, reviewing, or cleaning up RSpec tests; TDD discipline for all implementation | | rails-tdd-slices | Choosing the best first failing spec for a Rails change | | rails-bug-triage | Turning a bug report into a reproduction spec and fix plan | | rails-code-review | Reviewing Rails PRs, controllers, models, migrations, or queries — the subject is a specific file or changeset | | rails-architecture-review | Reviewing structure, boundaries, fat models/controllers — the question is about design or system shape, not a specific PR | | rails-stack-conventions | Writing Rails code for PostgreSQL + Hotwire + Tailwind stack | | refactor-safely | Restructuring code while preserving behavior | | create-prd | Planning a feature or writing requirements | | generate-tasks | Breaking a PRD into implementation tasks |
Skill Priority
When multiple skills could apply: TDD → Planning → Domain discovery → Process (refactor-safely) → Domain implementation (rails-*, ruby-*). Use rails-tdd-slices when the first failing spec is not obvious.
Key disambiguation signals:
rails-architecture-reviewvsrails-code-review: use architecture-review when the question is about system shape, service boundaries, or design patterns; use code-review when the subject is a concrete PR, file, or changeset.rails-tdd-slicesvsrspec-best-practices: use tdd-slices when the challenge is which test to write first; use rspec-best-practices when the challenge is how to write or improve a test.rails-context-engineeringbefore any other code-producing skill in an unfamiliar or existing codebase.
Fallback for ambiguous requests: If no clear skill match, default to rails-context-engineering to load codebase context, then re-evaluate based on findings.
Routing Examples
User: "There's a bug where orders placed at midnight sometimes get the wrong price."
Match: Concrete bug report with a reproduction path. See "Bug fix" workflow below.
Next skill: skills/testing/rails-bug-triage
User: "Help me improve this Rails app."
Match: Vague request, no clear skill. Use fallback: load context first.
Next skill: skills/context/rails-context-engineering
User: "I have a PR that adds a new controller, changes the Order model, adds a migration, and introduces a service object."
Match: Multi-concern changeset. Load context, then decompose into appropriate review skills.
Next skill: skills/context/rails-context-engineering
For additional routing examples (DDD-first features, GraphQL APIs, engines, edge cases), see assets/examples.md.
Typical Workflows
Sub-skills are invoked by stating their name as the next skill to apply, e.g. "Next skill: skills/workflows/rails-tdd-loop", before proceeding with that skill's instructions.
TDD Feature Loop (primary daily workflow) — use skills/workflows/rails-tdd-loop:
skills/context/rails-context-engineering → [CHECK: context loaded] → skills/workflows/rails-tdd-loop → PR
Feature (standard): skills/context/rails-context-engineering → [CHECK: context loaded] → skills/planning/create-prd → [CHECK: PRD approved] → skills/planning/generate-tasks → [CHECK: tasks complete] → skills/workflows/rails-tdd-loop
Bug fix: skills/testing/rails-bug-triage → [GATE: reproduction spec fails] → skills/workflows/rails-tdd-loop → fix → verify passes
For additional workflows (DDD-first, code review, engines, refactoring, GraphQL), see assets/workflows.md.
Assets
- assets/examples.md — 20+ routing examples covering ambiguous requests, multi-concern PRs, DDD-first features, engines, and edge cases
- assets/workflows.md — Extended workflow definitions for DDD-first, code review, engines, refactoring, and GraphQL
- docs/reference/skill-catalog.md — Complete skill catalog with trigger words, descriptions, and stage-based navigation
Related Skills
igmarin/rails-agent-skills
development
VerifiedTrustedCommunity
Entry point for Rails development workflows covering TDD, RSpec, Service Objects, DDD, GraphQL, Engines, and Code Quality. Use when the user asks about Ruby on Rails development patterns, needs RSpec test suites generated, wants service objects scaffolded, is setting up GraphQL schemas, performing Rails code review, refactoring .rb files, working with domain-driven design, implementing background jobs, conducting Rails security checks, or building Rails engines. Generates RSpec tests, structures service objects, enforces TDD workflows, configures GraphQL schemas, and coordinates domain-driven design patterns. Trigger keywords: Rails, RSpec, TDD, Rails testing, Rails refactor, Rails API, Rails code review, domain driven design, service objects, GraphQL, Rails engine, Ruby, .rb, background jobs, Rails migrations, Rails security check.
21SKILL.mdUpdated May 18, 2026
igmarin/release-engine
development
VerifiedTrustedCommunity
Use when shipping a Rails engine gem — FIRST run full test suite (`bundle exec rspec`) and fix ALL failures, verify gemspec metadata and dependencies match tested Rails/Ruby versions, dry-run: `gem build *.gemspec && gem push --dry-run *.gem` and verify contents, generate CHANGELOG.md organized by category (added/changed/deprecated/removed/fixed), produce step-by-step upgrade notes with before/after code, set semantic version in `lib/[engine_name]/version.rb`, document deprecations with migration paths, load release assets conditionally and state which one informed the output. Trigger words: version bump, changelog, deprecation, gemspec, upgrade, release, publish gem, ship gem.
21SKILL.mdUpdated May 9, 2026
igmarin/tdd
development
VerifiedTrustedCommunity
Orchestrates the full Rails TDD cycle with hard gates: test MUST exist, be run, and FAIL for the correct reason (e.g. undefined method, not syntax error) before any implementation code — propose minimal implementation and wait for user approval → verify test PASSES → run full suite with rubocop, brakeman, rspec all green → produce YARD documentation and self-reviewed PR; phases context/test design→implementation→iterate→finish. Use when practicing test-driven development, red-green-refactor, TDD workflow, writing tests before code, adding tests first, or building a Rails feature where specs must gate implementation.
19SKILL.mdUpdated Jun 5, 2026
igmarin/setup
development
VerifiedTrustedCommunity
Complete Rails project setup loop with hard gates: verify Ruby version matches .ruby-version, Bundler installed, database connection successful, all env vars loaded, and ALL external CI actions pinned to immutable commit SHAs (never mutable tags like @v4) → configure CI/CD pipeline with linting, testing, and security scanning → validate end-to-end with bundle install, db:create, db:migrate, rspec, and write SETUP_CHECKLIST.md; phases context/onboarding→CI/CD configuration→environment validation. Use when starting a new Rails project, running `rails new`, configuring a Gemfile or .ruby-version, setting up a development environment, or wiring up CI/CD for a Ruby on Rails app. Trigger: setup project, new Rails app, configure CI/CD, dev environment setup, rails new, Gemfile setup, .ruby-version, Ruby on Rails project bootstrap.
19SKILL.mdUpdated Jun 5, 2026