Help us improve
Share bugs, ideas, or general feedback.
From boorails
Diagnoses root causes of Ruby on Rails issues in performance (N+1 queries, slow endpoints), correctness, architecture, security, and reliability (flaky tests, regressions).
npx claudepluginhub kurenn/marketplace --plugin boorailsHow this skill is triggered — by the user, by Claude, or both
Slash command
/boorails:boo-diagnoseThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to move from symptom to root cause with evidence, not guesses.
Applies C++ Core Guidelines to write, review, or refactor C++ code. Enforces modern, safe, and idiomatic practices for C++17/20/23.
Share bugs, ideas, or general feedback.
Use this skill to move from symptom to root cause with evidence, not guesses.
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-resolution findings.
Never close diagnosis without at least one direct evidence source:
Use the bundled diagnostic runner for repeatable investigation:
scripts/run_diagnose.shscripts/run_diagnose.sh --project-dir /path/to/rails-appscripts/run_diagnose.sh --mode advisory --output-file tmp/diagnose-report.mdscripts/run_diagnose.sh --require-lsp (hard fail if ENABLE_LSP_TOOL!=1)Default behavior:
HIGH, MEDIUM, and LOW.tmp/rails-diagnose-<timestamp>/.In strict mode, HIGH findings return exit code 1.
Always end execution with:
Load references/external-resources.md for canonical debugging and Active Record references.