rails-debugger

Included with Lifetime

$97 forever

Use proactively when encountering Rails errors, test failures, build issues, or unexpected behavior. Analyzes errors, reproduces issues, and identifies root causes.

Code Review

What this skill does


# Rails Debugger

## Debugging Process

### 1. Gather Information

```bash
tail -100 log/development.log
bundle exec rspec --format documentation
bin/rails db:migrate:status
```

### 2. Analyze Stack Traces

**Identify the origin:**
- Find the first line in `app/` directory
- Note the file, line number, and method

**Common patterns:**

| Error | Likely Cause |
|-------|-------------|
| `NoMethodError: undefined method for nil:NilClass` | Missing association, nil return |
| `ActiveRecord::RecordNotFound` | ID doesn't exist, scoping issue |
| `ActiveRecord::RecordInvalid` | Validation failed |
| `ActionController::ParameterMissing` | Required param not sent |
| `NameError: uninitialized constant` | Missing require, typo |
| `LoadError` | File not found, autoload path issue |

### 3. Check Common Issues

**Database:**
```bash
bin/rails db:migrate:status
bin/rails db:schema:dump
```

**Dependencies:**
```bash
bundle check
bundle install
```

### 4. Isolate the Problem

**Reproduce in console:**
```ruby
user = User.find(123)
user.some_method  # Does it fail here?
```

**Binary search:**
- Comment out half the code
- Does error persist?
- Narrow down

### 5. Check Recent Changes

```bash
git log --oneline -20
git log -p --follow app/models/user.rb
git diff HEAD~5 app/models/user.rb
```

## Debugging Techniques

### Hypothesis Testing

1. Form specific, testable theories
2. Design minimal tests to prove/disprove
3. Document what you've ruled out

### State Inspection

```ruby
Rails.logger.debug { "DEBUG: user=#{user.inspect}" }
binding.irb  # Pause here (Rails 7+)
```

## Common Rails Issues

### N+1 Queries

```bash
grep "SELECT" log/development.log | sort | uniq -c | sort -rn
```

Fix: `User.includes(:posts)`

### Routing Issues

```bash
bin/rails routes | grep users
bin/rails routes -c users
```

### Callback Issues

```ruby
User._create_callbacks.map(&:filter)
User._save_callbacks.map(&:filter)
```

## Bug Report Validation

### Classification

| Status | Meaning |
|--------|---------|
| **Confirmed Bug** | Reproduced with clear deviation |
| **Cannot Reproduce** | Unable to reproduce |
| **Not a Bug** | Behavior is correct per spec |
| **Data Issue** | Problem with specific data |

## Output Format

1. **Reproduction Status** - Confirmed / Cannot Reproduce / Not a Bug
2. **Root Cause** - What's actually wrong (explain *why*)
3. **Evidence** - Specific logs, traces, or code
4. **Fix** - Minimal code changes
5. **Prevention** - How to avoid similar issues
6. **Verification** - Commands/tests to confirm fix

Files: 1

Size: 2.7 KB

Complexity: 11/100

Category: Code Review

Source: https://github.com/majesticlabs-dev/majestic-marketplace/tree/main/plugins/majestic-rails/skills/rails-debugger

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts