Debug with Tracepoint
Use when you need to know what a Ruby/Rails code path actually did at runtime - which methods ran, what arguments they got, what each one returned, and where an exception was first raised. Reach for this before adding puts/Rails.logger lines or reading call sites by hand, and whenever a value is wrong but you cannot tell which method produced it.
Install
npx skills add carlosdanielpohlod/rails_tracepoint_stack --skill debug-with-tracepointgit clone --depth 1 https://github.com/carlosdanielpohlod/rails_tracepoint_stack.git /tmp/rails_tracepoint_stack
mkdir -p ~/.claude/skills
cp -r /tmp/rails_tracepoint_stack/lib/rails_tracepoint_stack/templates ~/.claude/skills/debug-with-tracepointPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Debugging with rails_tracepoint_stack
Traces one block of code and hands back the call tree: every method your app
defined that ran, with its arguments, its return value, and any exception,
nested by call depth. Gems, the framework and stdlib are filtered out.
## When this beats the alternatives
| Question | Use this |
|---|---|
| "Which of these methods is returning nil?" | Yes - return values are the point |
| "Where did this exception actually start?" | Yes - the raise is tagged in the tree |
| "What is the real order of calls here?" | Yes - the tree shows nesting |
| "What is the value of one variable right here?" | No - a `binding.irb` is cheaper |
| "Is this endpoint slow?" | No - this measures nothing |
## Run it
One shot, no config file, no server restart, output bounded:
```bash
bin/rails runner '
session = RailsTracepointStack.capture(max_depth: 4) do
Order.find(42).recalculate!
end
puts session.to_tree
'
```
Reading the output:
```
Order#recalculate! (app/models/order.rb:88) {}
Order#apply_discount (app/models/order.rb:102) {"total":200.0}
Discount#rate_for (app/models/discount.rb:12) {"order":"#<Order id: 42>"}
-> null <- rate_for returned nil, which is the bug
-> 200.0
-> 200.0
3 calls, 3 returns, 0 raises, 2 classes
```
- indentation is call depth
- `-> value` is what the method on the line above returned
- `!! ArgumentError: message` marks where an exception was raisedDetails
- Skill name
debug-with-tracepoint- Repository
- carlosdanielpohlod/rails_tracepoint_stack
- Path
lib/rails_tracepoint_stack/templates/SKILL.md- Repo updated
- 28 July 2026
FAQ
What does the Debug with Tracepoint skill do?
Use when you need to know what a Ruby/Rails code path actually did at runtime - which methods ran, what arguments they got, what each one returned, and where an exception was first raised. Reach for this before adding puts/Rails.logger lines or reading call sites by hand, and whenever a value is wrong but you cannot tell which method produced it.
How do I install the Debug with Tracepoint skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add carlosdanielpohlod/rails_tracepoint_stack --skill debug-with-tracepoint. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Debug with Tracepoint popular?
It lives in carlosdanielpohlod/rails_tracepoint_stack, which has 43 GitHub stars and 4 forks.
Related skills
Motion Library
45ronkenx9/motion-library-skill
Use this when building or growing a library of motion-design techniques from real brand videos, when breaking down a motion reference shot by shot, or when turning that library into an original storyboard or concept for a brief. Do not use it to copy a reference.
Thermo Nuclear Code Quality Review
107Dimon94/skills
Run an extremely strict maintainability review for abstraction quality, giant files, and spaghetti-condition growth. Use for a thermo-nuclear code quality review, thermonuclear review, deep code quality audit, or especially harsh maintainability review.
Effect Ts
46joelhooks/effectts-skills
Write idiomatic Effect v4 TypeScript following official best practices from effect-solutions and the Effect source. Use when writing, reviewing, or refactoring Effect code: services (ServiceMap.Service), layers and dependency injection, error handling (Schema.TaggedErrorClass), data modeling (Schema.Class, branded types, variants), testing (@effect/vitest), HTTP clients (effect/unstable/http), CLI tools (effect/unstable/cli), config, observability, and project setup. Triggers on: 'Effect', 'effect-ts', '@effect/', 'Schema', 'ServiceMap', 'Layer', 'Effect.gen', 'Effect.fn', 'TaggedError', 'bran
Skills CLI Sync
43laststance/skills-desktop
Sync skills-desktop's AGENT_DEFINITIONS and UNIVERSAL_AGENT_IDS with the upstream vercel-labs/skills CLI, then update docs and validate. Use when bumping SKILLS_CLI_VERSION, mirroring a new upstream skills-CLI release, or when the agent list / universal set drifts from upstream agents.ts.
Information Architecture Audit
74mastepanoski/claude-skills
Audit or design the information architecture of a site/app — organization, labeling, navigation, search, content inventory, sitemaps, card sorting and tree testing, with prioritized findings.
Show Me
107Dimon94/skills
Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.