Script-first Ruby on Rails skills for safer shipping, faster diagnosis, and cleaner delivery — packaged as a Claude Code plugin.

Seven boo-* skills covering the Rails dev lifecycle from design to release. Each skill ships an executable script for deterministic execution and a SKILL.md that orchestrates the workflow inside Claude Code or Codex.

Most AI workflows stop at suggestions. BooRails executes the Rails workflow end-to-end and returns evidence.

• Script-first framework execution (Diagnose → Security → Safety → Quality Gates)
• Explicit execution summary and report files
• Gem bootstrap feedback (target/present/installed/failed)
• LSP-aware guidance for stronger symbol-level analysis

• /boo-framework — orchestrates the full workflow, runs gem bootstrap, and produces a consolidated summary report.

claude plugin marketplace add kurenn/marketplace   # one-time per user
claude plugin install boorails@kurenn              # one-time install

After install, restart your Claude Code session and the seven /boo-* skills appear in the slash menu.

git clone https://github.com/kurenn/boorails ~/workspace/boorails
claude --plugin-dir ~/workspace/boorails

If you were using the manual shell-script install (install_skills_codex_claude.sh) and want to stay on it, those scripts are still in legacy/. They install the OLD rails-* skill names from the v0.2.0 tag. New work should switch to the marketplace install above.

When a new version is released, pull it via the marketplace:

# Refresh the marketplace cache (picks up new versions from marketplace.json)
claude plugin marketplace update kurenn

# Update boorails to the latest released version
claude plugin update boorails

Restart your Claude Code session after updating so the slash menu picks up the new version.

Verify which version you're on:

claude plugin list | grep -A3 boorails@kurenn

To pin to a specific older version (e.g. roll back to the pre-rename rails-* skills on v0.2.0), clone the tag locally:

# v0.2.0 (legacy rails-* skill names — non-plugin install via shell scripts)
git clone https://github.com/kurenn/boorails --branch v0.2.0 ~/.boorails
~/.boorails/legacy/install_skills_codex_claude.sh --target both --force

# v2.0.0+ (new boo-* skill names via plugin)
git clone https://github.com/kurenn/boorails --branch v2.0.0 ~/workspace/boorails-2.0.0
claude --plugin-dir ~/workspace/boorails-2.0.0

cd /path/to/your/rails_app

export ENABLE_LSP_TOOL=1

/boo-framework
/boo-security
/boo-diagnose
/boo-quality
/boo-safety
/boo-alternatives
/boo-dx

Most common entrypoint: /boo-framework.

Open:

• tmp/rails-framework-workflow-<timestamp>/00-summary.md

It links to:

• 00-framework-gems.md
• 01-diagnose.md
• 02-security.md
• 03-safety.md
• 04-quality-gates.md

After plugin install, the scripts live under your Claude plugins cache. From any Rails app root:

PLUGIN=~/.claude/plugins/cache/kurenn/boorails/2.0.0
bash "$PLUGIN/skills/boo-framework/scripts/run_framework_workflow.sh" --project-dir "$PWD" --mode strict --gemset full --require-lsp
bash "$PLUGIN/skills/boo-diagnose/scripts/run_diagnose.sh" --project-dir "$PWD" --require-lsp
bash "$PLUGIN/skills/boo-security/scripts/run_security_audit.sh" --project-dir "$PWD" --require-lsp
bash "$PLUGIN/skills/boo-safety/scripts/safety_check.sh" --project-dir "$PWD" --require-lsp
bash "$PLUGIN/skills/boo-quality/scripts/run_gates.sh" --project-dir "$PWD" --require-lsp

• Default: installs missing gems (--gemset full)
• Core-only: --gemset minimal
• Dry-run only: --gem-dry-run
• Disable install: --no-auto-install-gems

./scripts/ci_smoke.sh

• Claude Code
• Codex (via the legacy install path)

If you've been using boorails via install_skills_codex_claude.sh, the slash commands you've been using (/rails-security, /rails-framework, etc.) no longer exist under those names in 2.0. Two options:

1. Switch to the marketplace install (recommended) — see CHANGELOG.md for the full migration table.
2. Stay on v0.2 — git checkout v0.2.0 and run the legacy install script. The old rails-* skill names still work on that tag.

MIT. See LICENSE.