slow

Run a read-only Rails performance audit detecting slow queries, N+1s, and coverage gaps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/benjaminfauchald/Tracklister --skill slow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slow
Source: https://github.com/benjaminfauchald/Tracklister/tree/main/.claude/skills/slow
Command: npx skills add https://github.com/benjaminfauchald/Tracklister --skill slow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill performs a thorough, read-only performance audit to find slow queries, N+1s, uncached heavy counts, log-indicated anti-patterns, and gaps in query-budget test coverage so teams can prioritize impactful fixes without modifying code.

Core Features & Use Cases

  • Automated Diagnostics: Run the repository's performance rake task, parse logs, and surface top slow queries and sequential scans.
  • Anti-pattern Detection: Scan controllers, views, and components for N+1 patterns, service/db calls in views, UUID casting issues, and problematic SET LOCAL usage.
  • Cross-reference & Prioritization: Correlate findings with historical "SYSTEM SLOW" GitHub issues and the Bullet allowlist to identify recurring problems and provide prioritized remediation recommendations.

Quick Start

Request a read-only comprehensive performance audit that runs the rake performance:audit, scans code and logs for anti-patterns, cross-references SYSTEM SLOW issues, and returns a prioritized PERFORMANCE GUARDIAN REPORT.

Frequently Asked Questions about slow

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

FAQPage Schema
How do I run a performance audit to detect N+1 queries and slow database calls in a Rails app?

Run a comprehensive performance audit to detect slow queries, N+1 patterns, and uncached counts by executing rake performance:audit, scanning logs, and cross-referencing GitHub issues to produce a prioritized read-only report with file:line references.

What is the best way to correlate recurring performance regressions with historical GitHub issues?

Cross-reference historical SYSTEM SLOW GitHub issues during a performance audit to identify recurring problems, correlate findings with the Bullet allowlist, and generate a prioritized remediation report for engineering reviews.

Does this performance audit modify code or database schemas during incident response?

This performance audit is strictly read-only and requires explicit approval before creating any GitHub issues, ensuring no code modifications or database changes occur during incident response or CI-driven diagnostics.

How do I find uncached heavy counts and problematic SET LOCAL usage in my Ruby on Rails repository?

Scan controllers, views, and components for uncached heavy counts, problematic SET LOCAL usage, and service or database calls in views to locate performance hotspots and anti-patterns with specific file:line references.

Can I use this audit to identify gaps in query-budget test coverage?

Yes, the audit detects gaps in query-budget test coverage while scanning for anti-patterns like UUID casting issues and sequential scans, returning a prioritized PERFORMANCE GUARDIAN REPORT for engineering teams.