skills.rest
slbug
slbugCOMMUNITY
Explore all skills by this author →
GitHub

rb:techdebt

Detect Ruby/Rails/Grape technical debt patterns like duplicated queries and callback sprawl.

7|Updated Mar 22, 2026
Search Tags:#architecture#refactoring#ruby#rails#code-smells#techdebt
One-click install
npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill rb-techdebt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rb:techdebt
Source: https://github.com/slbug/claude-ruby-grape-rails/tree/main/plugins/ruby-grape-rails/skills/techdebt
Command: npx skills add https://github.com/slbug/claude-ruby-grape-rails --skill rb-techdebt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and understand Ruby/Rails/Grape technical debt patterns in a codebase to guide safe refactors.

Core Features & Use Cases

  • Detect duplicated query logic across models and services
  • Flag callback-driven side effects and services with too many responsibilities
  • Highlight stale abstractions and gaps in legacy tests

Quick Start

Review the codebase to surface Ruby/Rails/Grape technical debt patterns and suggest concrete refactors.

Frequently Asked Questions about rb:techdebt

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

FAQPage Schema
How do I identify Ruby tech debt in a large Rails codebase?▼

Identify Ruby tech debt by reviewing models and services to detect duplicated query logic, flag callback-driven side effects, and highlight stale abstractions for concrete refactoring guidance.

What are common Rails code smells that indicate technical debt?▼

Common Rails code smells include duplicated query logic across models, callback sprawl causing hidden side effects, and services with too many responsibilities that signal aging abstractions.

How do I detect duplicated query logic across Ruby models and services?▼

Detect duplicated query logic by reviewing the codebase to surface repeated database query patterns across Ruby models and services, providing actionable guidance to consolidate them.

Does this tech debt analysis work with Grape and older Rails services?▼

Yes, this tech debt analysis works with Grape and large aging Rails services, specifically targeting legacy abstractions, missing tests, and callback sprawl where debt accumulates.

How do I refactor Rails callbacks that are causing side effects?▼

Refactor Rails callbacks by flagging callback-driven side effects and services with too many responsibilities, then applying the actionable refactoring guidance surfaced during the codebase review.

When should I look for technical debt in a Ruby codebase?▼

Look for technical debt when maintaining large Rails services with many models, callbacks, and aging abstractions, specifically to find stale code, missing tests, and duplicated logic before refactoring.

Related Skills

Explore More Software Engineering Skills→
slbugslbug
7

rb:examples

Extract representative Ruby/Rails/Grape code examples with file paths.

Community
Basic
htlin222htlin222
77

refactor

Refactor code to reduce technical debt and improve maintainability.

Community
Intermediate
SebastienDegodezSebastienDegodez
8

test-refactoring-catalog

Refactor Python test code while preserving behavioral coverage.

Community
Advanced
loren-arthurloren-arthur

desloppify

Scan codebases to identify technical debt and code smells across 28 programming languages.

Community
Intermediate