rb:trace

Trace request execution paths in Ruby on Rails, Grape APIs, and Sidekiq jobs.

7|Updated Mar 22, 2026

Search Tags:#debugging #trace #rails #sidekiq #grape #request-flow

Ready to run

npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill rb-trace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rb:trace
Source: https://github.com/slbug/claude-ruby-grape-rails/tree/main/plugins/ruby-grape-rails/skills/rb-trace
Command: npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill rb-trace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps developers quickly understand how a request, API call, background job, or service flow moves through a Ruby on Rails, Grape, and Sidekiq codebase, revealing where values change or side effects occur.

Core Features & Use Cases

Entry‑point identification: Detects routes, mounted Grape APIs, controller actions, service objects, models, jobs, broadcasts, and cache writes.
Step‑by‑step trace: Generates a concise chain of file paths that illustrate the execution path.
Use case: When a bug appears after a request, use this skill to map the exact code path from the HTTP endpoint to the point where the unexpected value is introduced.

Quick Start

Trace the flow of the update_user method starting from the incoming HTTP request.

Frequently Asked Questions about rb:trace

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I trace a request flow across Rails, Grape, and Sidekiq?▼

Trace request flow across Rails, Grape, and Sidekiq by statically analyzing entry points to map routes, controllers, services, models, and jobs into a concise step-by-step chain of file locations. It outputs a readable trace without executing code.

What is the best way to debug a request execution path in Ruby on Rails?▼

Debug a request execution path in Ruby on Rails by mapping the exact code route from the HTTP endpoint to the point where an unexpected value is introduced. It statically extracts arguments and identifies entry points like controllers, models, and cache writes.

How does static analysis map Sidekiq jobs and Grape APIs to file paths?▼

Static analysis maps Sidekiq jobs and Grape APIs to file paths by detecting mounted API endpoints and background job entry points, then chaining the file locations to reveal where values change or side effects occur during execution.

Can I trace a Ruby on Rails code path without running the application code?▼

You can trace a Ruby on Rails code path without running code because the trace is generated entirely through static analysis of entry points and argument extraction, producing a readable execution chain of file locations.

How do I find where a side effect occurs during a Grape API call?▼

Find where a side effect occurs during a Grape API call by tracing the request execution path from the mounted API endpoint through services and models, generating a concise chain of file paths that illustrate the execution route.

Does this request flow tracer support detecting cache writes and broadcasts?▼

The request flow tracer supports detecting cache writes and broadcasts as entry points, mapping them alongside routes, controllers, services, and models to produce a step-by-step trace of file locations.