ワンクリックでManusで任意のスキルを実行

rails-verify

スター0

フォーク0

更新日2026年6月7日 09:19

Verify that an existing Ruby on Rails application actually works: it eager-loads cleanly, boots a real web server that answers the /up health check, and passes its test suite. Use this skill when the user wants to confirm a Rails app is healthy, sanity-check a checkout or a freshly cloned repo, gate a deploy, or run a "does this thing even boot?" check — against an app that ALREADY EXISTS. Do NOT use it to create or scaffold a new app (use rails-bootstrap for that); the rails-bootstrap skill already calls this same verification at the end of a bootstrap, so there is no need to run both back to back.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

jcuervo

jcuervo/rails-bootstrap

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Rails Verify

Confirm that an existing Rails app is healthy. This is the standalone counterpart to the verification step inside rails-bootstrap — both call the same shared implementation (shared/lib/verify.sh, verify::run), so "verified" means the same thing whether an app was just generated or has been around for a year.

When to use

A user clones a Rails repo and wants to know it boots before working on it.
Before a deploy or merge, as a quick "loads + boots + tests green" gate.
After a dependency bump or Ruby upgrade, to confirm nothing regressed.

For creating a new app, use rails-bootstrap instead — it runs this verification automatically as its final step.

What it checks, in order

Loads — bin/rails runner 'Rails.application.eager_load!' catches autoload and load-time errors.
Boots — starts a real bin/rails server and waits for HTTP 200 on the Rails 8 /up health endpoint, then shuts it down. This exercises middleware, routes, and the asset pipeline — not just class loading.
Tests — runs the suite (bin/rails test, or bundle exec rspec if the app uses RSpec). A red suite is reported as a failure.

Usage

scripts/verify_app.sh --path /path/to/app [--test minitest|rspec] [--allow-test-failures]

--path defaults to the current directory.
--test defaults to minitest; pass rspec for RSpec apps.
--allow-test-failures downgrades a red suite from fatal to a warning (off by default — verification should fail loudly).

Report whether each stage passed, and on failure surface the actual error rather than a generic "verification failed." A check that hides the breakage is worse than no check.

このリポジトリの他の Skills

同じリポジトリ

rails-bootstrap

jcuervo/rails-bootstrap

Bootstrap a new, production-leaning Ruby on Rails application on the latest Rails (8.1.x) and Ruby (4.0.x), with version pinning, sensible defaults, and verification. Use this skill whenever the user wants to start, scaffold, generate, or set up a new Rails app, mentions `rails new`, asks for a Rails project skeleton or starter, or says things like "spin up a Rails API", "create a new Rails 8 app", or "bootstrap a Rails project" — even if they don't name the skill explicitly. Do NOT use it for modifying an existing Rails app, upgrading Rails versions, or non-Rails projects. To only verify an app that already exists, use the rails-verify skill instead.

2026-06-070

name

rails-verify

description

Rails Verify

When to use

A user clones a Rails repo and wants to know it boots before working on it.
Before a deploy or merge, as a quick "loads + boots + tests green" gate.
After a dependency bump or Ruby upgrade, to confirm nothing regressed.

For creating a new app, use rails-bootstrap instead — it runs this verification automatically as its final step.

What it checks, in order

Loads — bin/rails runner 'Rails.application.eager_load!' catches autoload and load-time errors.
Boots — starts a real bin/rails server and waits for HTTP 200 on the Rails 8 /up health endpoint, then shuts it down. This exercises middleware, routes, and the asset pipeline — not just class loading.
Tests — runs the suite (bin/rails test, or bundle exec rspec if the app uses RSpec). A red suite is reported as a failure.

Usage

scripts/verify_app.sh --path /path/to/app [--test minitest|rspec] [--allow-test-failures]

--path defaults to the current directory.
--test defaults to minitest; pass rspec for RSpec apps.
--allow-test-failures downgrades a red suite from fatal to a warning (off by default — verification should fail loudly).

Report whether each stage passed, and on failure surface the actual error rather than a generic "verification failed." A check that hides the breakage is worse than no check.