← ClaudeAtlas

rails-audit-skilllisted

Perform comprehensive technical reviews of Ruby on Rails applications. Runs automated analysis tools (RubyCritic, Brakeman, bundler-audit, Gitleaks, Debride, linters, SimpleCov, Rails stats, Rails ERD), analyzes code for architecture, security, authorization (Pundit/CanCanCan), dead code, and design issues, and produces a structured markdown report with prioritized findings and a 0-10 score. Use when the user requests a tech review, code audit, project assessment, or quality analysis of a Rails application.
rubyroidlabs/rails-audit-skill · ★ 15 · Code & Development · score 75
Install: claude install-skill rubyroidlabs/rails-audit-skill
# Rails Tech Review Skill Perform comprehensive technical reviews of Ruby on Rails applications. This skill runs automated analysis tools, inspects source code manually, and produces a structured audit report with prioritized findings. ## Audit Scope The audit can be run in two modes: 1. **Full Application Audit**: Analyze entire Rails application (default) 2. **Targeted Audit**: Analyze specific files or directories ## Execution Flow ### Phase 1: Project Discovery 1. **Verify this is a Rails project.** Check for `config/application.rb`, `Gemfile`, and `app/` directory. If none of these exist, immediately abort and tell the user: "This does not appear to be a Ruby on Rails project. This skill only supports Rails applications." 2. Extract key metadata: - Ruby version (from `.ruby-version`, `Gemfile.lock`, or `.tool-versions`) - Rails version (from `Gemfile.lock` — look for `rails (` entry) - Database adapter (from `config/database.yml` or `Gemfile.lock`) - Background job framework (check Gemfile for Sidekiq, GoodJob, DelayedJob, Resque) - Frontend setup (check `package.json`, `app/javascript/`, `app/assets/`) - CI/CD (check `.github/workflows/`, `.gitlab-ci.yml`, `Jenkinsfile`) - Test framework (check for `spec/` directory → RSpec, `test/` directory → Minitest) - Infrastructure signals (check for `Procfile`, `Dockerfile`, `docker-compose.yml`, `app.json`) 3. Attempt `bundle install` to verify dependencies resolve. Note any failures. 4. Attempt to