omc-rails-autopilot

Orchestrate Rails feature development across tests, implementation, reviews, and delivery.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Grupo-AFAL/claude-plugins --skill omc-rails-autopilot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-rails-autopilot
Source: https://github.com/Grupo-AFAL/claude-plugins/tree/main/rails-tools/skills/omc-rails-autopilot
Command: npx skills add https://github.com/Grupo-AFAL/claude-plugins --skill omc-rails-autopilot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automates and enforces a complete, auditable Rails feature delivery workflow so teams don't lose work, skip critical quality gates, or ship undocumented changes when implementing SmartSuite user stories.

Core Features & Use Cases

  • Structured 10-phase workflow: story fetch and branch isolation, TDD-first test creation, implementation, UI integration, iterative DHH AI reviews, visual verification, quality gates, docs, and final review.
  • Project-scoped SmartSuite integration: selects or validates stories by project ID, updates status, and links PRs for traceability.
  • Safety and preservation: records phase progress in a state file, creates git worktrees and early WIP pushes to protect work, and enforces pre-commit and pre-completion verification gates.
  • Use case: Start a full autonomous run from a story code or "next" to produce tests, implementation, screenshots, documentation, a PR, and SmartSuite updates without skipping required phases.

Quick Start

Invoke the autopilot with a story ID or the keyword next to run the full ten-phase implementation and deliver a PR and documentation.

Frequently Asked Questions about omc-rails-autopilot

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Rails feature development from requirements to pull request?

Automated Rails feature delivery orchestrates a ten-phase workflow covering story fetch, TDD-first test creation, implementation, UI integration, AI code reviews, visual verification, and quality gates to produce a PR and documentation automatically.

What is the best way to enforce TDD and quality gates in a Rails project?

Enforcing TDD and quality gates in a Rails project requires a structured workflow that creates tests before implementation, runs pre-commit checks including Rubocop and Brakeman, and performs iterative code reviews to block incomplete changes from shipping.

Does autonomous Rails delivery work with Hotwire and Bali ViewComponents?

Autonomous Rails delivery supports projects using Hotwire and Bali ViewComponents, integrating UI components during implementation and performing E2E visual verification to confirm interface behavior before finalizing the pull request.

Can I use git worktrees to isolate Rails feature branches during automated development?

Git worktrees isolate Rails feature branches during automated development, protecting work-in-progress with early WIP pushes and recording phase progress in a state file so no work is lost across the delivery lifecycle.

How do SmartSuite story workflows integrate with Rails pull requests?

SmartSuite story workflows integrate with Rails pull requests by fetching stories using project IDs, validating requirements, updating story statuses, and linking completed PRs back to SmartSuite for full traceability throughout the development cycle.

What are the limitations of automated Rails feature delivery?

Automated Rails feature delivery is limited to projects using Pundit authorization, Hotwire, and Bali ViewComponents, requiring SmartSuite-backed story workflows and specific pre-commit quality gates to function correctly without skipping required phases.