菜单
Applies implementation safety checklists for Ruby on Rails code changes. Use when writing or reviewing code that touches user input, authorization, database migrations, background jobs, external APIs, or production-critical paths. Triggers on secure, safe migration, pre-merge checklist, rollout risk, data integrity, and production hardening.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Generates and compares implementation alternatives for Ruby on Rails decisions. Use when choosing between architectural approaches, query patterns, service boundaries, framework features, or rollout strategies. Triggers on alternatives, tradeoffs, option A/B, design choice, compare approaches, or should we use X vs Y.
Performs root-cause diagnosis for Ruby on Rails issues across performance, correctness, architecture, security, and reliability. Use when requests involve bugs, regressions, N+1 queries, slow endpoints, flaky tests, unexpected behavior, or unclear failures. Triggers on words like diagnose, debug, investigate, root cause, slowdown, flaky, regression, N+1, timeout.
Optimizes developer experience in Ruby on Rails workflows without compromising safety or quality. Use when teams face slow feedback loops, repetitive tasks, unclear errors, onboarding friction, or low development flow. Triggers on DX, developer productivity, faster feedback, workflow friction, onboarding, and ergonomics.
Defines the operating framework for AI-assisted Ruby on Rails development. Use when planning architecture, framing implementation strategy, creating multi-step workflows, coordinating specialized Rails skills, or aligning a team on a consistent delivery model. Triggers on requests like framework definition, implementation workflow, Rails standards, feature planning, or system-level guidance.
Runs and interprets quality gates for Ruby on Rails delivery. Use when validating PR readiness, release safety, or implementation quality across tests, linting, security, and performance checks. Triggers on quality gate, readiness, release check, CI parity, lint, test suite, security scan, or pre-merge validation.
Deep security workflow for Ruby on Rails applications. Use when auditing or implementing controls for XSS, SQL injection, CSRF, file uploads, command injection, session/cookie hardening, and security monitoring. Triggers on appsec audit, security review, OWASP, CSP, CSRF, upload hardening, or secure coding requests.
| name | boo-safety |
| description | Applies implementation safety checklists for Ruby on Rails code changes. Use when writing or reviewing code that touches user input, authorization, database migrations, background jobs, external APIs, or production-critical paths. Triggers on secure, safe migration, pre-merge checklist, rollout risk, data integrity, and production hardening. |
Use this skill before finalizing code to reduce production risk and prevent common Rails failure patterns.
Strongly recommend enabling LSP before running this skill:
ENABLE_LSP_TOOL=1 in the shell running Claude/Codex.ruby-lsp and/or solargraph).If LSP is not enabled, continue execution but mark reduced confidence for symbol-level static checks.
Do not mark ready if any blocker exists:
Use the bundled checker for repeatable safety audits:
scripts/safety_check.shscripts/safety_check.sh --project-dir /path/to/rails-appscripts/safety_check.sh --mode advisoryscripts/safety_check.sh --output-file tmp/safety-report.mdscripts/safety_check.sh --require-lsp (hard fail if ENABLE_LSP_TOOL!=1)Default behavior:
tmp/rails-safety-check-<timestamp>/.In strict mode, any blocker returns exit code 1.
Always end execution with:
Load references/external-resources.md for Rails Security and OWASP-aligned checks.