القائمة
Root-cause analysis for Ruby/Rails/Grape bugs whose cause is unknown. Triggers: "why is this broken", "root cause", "error analysis". Do NOT use for: perf, tracing.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | rb:investigate |
| description | Root-cause analysis for Ruby/Rails/Grape bugs whose cause is unknown. Triggers: "why is this broken", "root cause", "error analysis". Do NOT use for: perf, tracing. |
| argument-hint | <bug description> |
| effort | high |
Run a structured investigation instead of guessing.
Read ${CLAUDE_SKILL_DIR}/references/discipline.md and
${CLAUDE_SKILL_DIR}/references/error-patterns.md. Apply the
verify-loop discipline + error-classification rubric as the
canonical procedure.
bundle exec rspec path/to/spec.rb:LINE or bin/rails testbundle exec rails runnerpsql for SQL inspectionredis-cli for queue/cache inspectionWrite a short investigation report with:
/rb:plan or /rb:quick)This is a skill (/rb:investigate), not an agent. Do NOT spawn
investigate or rb-investigate via the Agent tool. For agent-based deep
investigation, use deep-bug-investigator
(subagent_type: "ruby-grape-rails:deep-bug-investigator"). When spawning,
pass an explicit output path in the prompt
(.claude/investigations/deep-bug-investigator/{slug}-{datesuffix}.md);
the agent writes its findings to that file and returns a ≤300-word chat
summary. Read the file for the full report.
If the agent's return text matches the pause signature in
${CLAUDE_PLUGIN_ROOT}/references/agent-resume.md, follow that protocol
to resume the agent before treating the artifact as missing.
## Ruled Out scratchpad
section FIRST. Don't re-run grep / Read on file already eliminated.| Need | Reference |
|---|---|
| investigation discipline (no guessing, structured tracks) | ${CLAUDE_SKILL_DIR}/references/discipline.md |
| investigation report template (Ralph Wiggum checklist + Root Cause + Fix) | ${CLAUDE_SKILL_DIR}/references/investigation-template.md |
| common error-pattern catalog | ${CLAUDE_SKILL_DIR}/references/error-patterns.md |
| quick debug commands + common-fix recipes (string vs atom keys, eager-load gaps, nil propagation) | ${CLAUDE_SKILL_DIR}/references/debug-commands.md |
| production-incident triage flow (payload → reproduction → fix → verify → capture) | ${CLAUDE_SKILL_DIR}/references/incident-playbook.md |
/rb:perf (performance analysis)/rubydoc-fetcher (cheap doc lookup)/rb:state-audit (request-state hygiene)/rb:runtime (Tidewave runtime introspection)/rb:techdebt (tech-debt logging)CONTRIBUTOR TOOL - Track CC changelog, extract new versions since last check, analyze impact on plugin (breaking changes, opportunities, deprecations). Run periodically or before releases. NOT part of the distributed plugin.
CONTRIBUTOR TOOL - Check the plugin against current cached Claude Code docs. Use before releases or after Claude docs changes to separate real schema drift from stale local assumptions. Not part of the distributed plugin.
Guide plugin development workflow for this repo. Use when editing shipped plugin files under plugins/ruby-grape-rails/, release/docs metadata, or contributor tooling under .claude/.
Analyze observational skill-effectiveness signals across scanned sessions. Use for exploratory monitoring and recommendation triage, not as a release gate.
Initializing the Ruby/Rails/Grape plugin: writes stack notes (queues, ORM-per-package, layout) into CLAUDE.md. Triggers: "initialize plugin", "setup ruby plugin", "configure Claude for Rails".
Walking a user through the Ruby/Rails/Grape plugin commands, capabilities, and workflow. Tutorial-style intro for newcomers who want to learn what the plugin offers rather than tackle a specific task.