Rails Validation

Set up named quality gate commands that act as repeatable CI-style checks for a Rails project, then run them in parallel and report results.

When to Use

• After building new functionality or making significant changes
• Before marking a task complete or submitting a PR
• When setting up quality gates for a new Rails project
• When a check command needs to change (new test runner, new linter config)
• When the user asks "does everything pass?" or "run all checks"

When NOT to Use

• One-off exploration commands — use Bash directly
• Deploy steps — use the deployment workflow instead

Standard Rails Quality Gates