rb:verify

Run prioritized Ruby, Rails, or Grape verification stacks stopping at first failure.

7|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill rb-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rb:verify
Source: https://github.com/slbug/claude-ruby-grape-rails/tree/main/plugins/ruby-grape-rails/skills/verify
Command: npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill rb-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill runs a prioritized verification pipeline to ensure completed Ruby, Rails, or Grape code meets autoloading, style, security, test, type, and migration requirements before merging or release. It centralizes tool selection, detects project-native verification wrappers when present, falls back to direct tooling when needed, and halts at the first failing check so developers get a clear next step.

Core Features & Use Cases

  • Ordered Verification Stack: Enforces the sequence Zeitwerk → Lint → Security → Tests → Types → Database → Optional diff-scoped pass so failures are deterministic and easy to address.
  • Project-aware Tool Selection: Re-detects project-native composite runners and honors cached runtime flags for standardrb, rubocop, brakeman, pronto, and test frameworks.
  • Fallbacks & Failure Handling: Falls back from wrapper to direct commands when wrappers are unavailable or broken and provides actionable remediation and re-run guidance.
  • Use Cases: Pre-commit sanity checks, CI job replacement or augmentation, local pre-PR verification, and release gating for Rails apps and libraries.

Quick Start

Run the full verification stack for the current repository and report the first failing check.

Frequently Asked Questions about rb:verify

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

FAQPage Schema
How do I run lint, security scans, and tests for a Rails project in one pass?

To verify Ruby or Rails code in one pass, run a prioritized verification stack that checks autoloading, lint, security, tests, types, and database migration status, stopping at the first failing check. This enforces a deterministic Zeitwerk to migration sequence.

What is the correct order for running RuboCop, Brakeman, and RSpec during CI?

The correct verification order for CI is Zeitwerk autoloading first, then lint via RuboCop or standardrb, then security scans via Brakeman, followed by tests with RSpec or Minitest, and finally type checks and database migration status checks.

Does this verification workflow support Grape projects or only full Rails applications?

This verification workflow supports full Rails applications, Ruby libraries, and Grape projects. It detects project-native composite runners and runtime flags, falling back to direct commands like standardrb and brakeman when wrappers are unavailable.

How can I automate pre-commit checks for Ruby code style and security vulnerabilities?

Automate pre-commit checks by running a verification stack that enforces lint via standardrb or rubocop and security via brakeman before tests. It detects cached runtime flags and provides actionable remediation guidance upon failure.

Why does my Rails verification pipeline halt before running the test suite?

A verification pipeline halts before tests because it enforces a strict ordered stack: Zeitlek, lint, and security checks must pass first. This deterministic halt ensures style and security failures are addressed before running RSpec or Minitest.

Can I use standardrb instead of rubocop for linting in my Ruby verification stack?

Yes, you can use standardrb instead of rubocop. The verification stack detects project-native composite runners and honors cached runtime flags for both standardrb and rubocop, falling back to direct commands if wrappers are broken.