code-review
/code-review
Analyzes Rails code quality, architecture, and patterns without modifying code. Use when the user wants a code review, quality analysis, architecture audit, or when user mentions review, audit, code quality, anti-patterns, or SOLID principles. WHEN NOT: Actually implementing fixes (use specialist agents), writing new tests (use rspec-agent), or generating new features.
- Author
- ThibautBaissac ↗
- Repository
- rails_ai_agents ↗
- Licence
- MIT
- Last repository change
- 01.06.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 01.06.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Analyzes Rails code quality, architecture, and patterns without modifying code. Use when the user wants a code review, quality analysis, architecture audit, or when user mentions review, audit, code quality, anti-patterns, or SOLID principles. WHEN NOT: Actually implementing fixes (use specialist agents), writing new tests (use rspec-agent), or generating new features.
Arguments
/code-review [file or directory path]
Original author description
Analyzes Rails code quality, architecture, and patterns without modifying code. Use when the user wants a code review, quality analysis, architecture audit, or when user mentions review, audit, code quality, anti-patterns, or SOLID principles. WHEN NOT: Actually implementing fixes (use specialist agents), writing new tests (use rspec-agent), or generating new features.
How it works
- Review Process
- Anti-Pattern Examples
- Review Checklist
SKILL.md preview
---
name: code-review
description: >-
Analyzes Rails code quality, architecture, and patterns without modifying
code. Use when the user wants a code review, quality analysis, architecture
audit, or when user mentions review, audit, code quality, anti-patterns,
or SOLID principles. WHEN NOT: Actually implementing fixes (use specialist
agents), writing new tests (use rspec-agent), or generating new features.
context: fork
agent: general-purpose
model: sonnet
allowed-tools: Read, Grep, Glob, Bash
user-invocable: true
argument-hint: "[file or directory path]"
---
# Code Review
You are an expert code reviewer specialized in Rails applications.
You NEVER modify code — you only read, analyze, and report findings.
## Review Process
### Step 1: Run Static Analysis
```bash
bin/brakeman
bin/bundler-audit
bundle exec rubocop
```
### Step 2: Analyze Code
Read and evaluate against these focus areas:
1. **SOLID Principles** — SRP violations, hard-coded conditionals, missing DI
2. **Rails Anti-Patterns** — Fat controllers/models, N+1 queries, callback hell
3. **Security** — Mass assignment, SQL injection, XSS, missing authorization
4. **Performance** — Missing indexes, inefficient queries, caching opportunities
5. **Code Quality** — Naming, duplication, method complexity, test coverage
### Step 3: Structured Feedback
Format your review as:
1. **Summary:** High-level overview
2. **Critical Issues (P0):** Security, data loss risks
3. **Major Issues (P1):** Performance, maintainability
4. **Minor Issues (P2-P3):** Style, improvements
5. **Positive Observations:** What was done well
For each issue: **What** → **Where** (file:line) → **Why** → **How** (code example)
## Anti-Pattern Examples
**Fat Controller → Service Object:**
```ruby
# Bad
class EntitiesController < ApplicationController
def create
@entity = Entity.new(entity_params)
@entity.calculate_metrics
@entity.send_notifications
if @entity.save then ... end
end
end
# Good
class EntitiesController < ApplicationController
def create
result = Entities::CreateService.call(entity_params)
end
end
```
**N+1 Query → Eager Loading:**
```ruby
# Bad
@entities.each { |e| e.user.name }
# Good
@entities = Entity.includes(:user)
```
**Missing Authorization:**
```ruby
# Bad
@entity = Entity.find(params[:id])
# Good
@entity = Entity.find(params[:id])
authorize @entity
```
## Review Checklist
- [ ] Security: Brakeman clean
- [ ] Dependencies: Bundler Audit clean
- [ ] Style: RuboCop compliant
- [ ] Architecture: SOLID principles respected
- [ ] Patterns: No fat controllers/models
- [ ] Performance: No N+1, indexes present
- [ ] Authorization: Pundit policies used
- [ ] Tests: Coverage adequate
- [ ] Naming: Clear, consistent
- [ ] Duplication: No repeated code
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · ThibautBaissac/rails_ai_agents | 100 | MIT |
| microsoft/aspire | 100 | MIT |
| kdlbs/kandev | 100 | AGPL-3.0 |
| dotnet/runtime | 100 | MIT |
| drosam/agents | 100 | MIT |
| ggml-org/llama.cpp | 100 | MIT |
| ShamelesAbyss/Nyx | 100 | Apache-2.0 |
| dzhng/jevgrep | 100 | MIT |
| iuliandita/skills | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 17f5356e8504 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100clean-code-principles
SOLID principles, design patterns, DRY, KISS, and clean code fundamentals. Use when reviewing architecture, checking code quality, refactoring, or discussing design decisions. Triggers on "review architecture", "check code quality", "SOLID principles", "design patterns", or "clean code". - 100go-code-audit
WHEN: User asks for a code quality audit, code review, or wants to find code smells, anti-patterns, or non-idiomatic Go code in their project. Also when asked "how good is this code?" or "audit my code." WHEN NOT: When the user wants to fix bugs, run tests, or just lint (use… - 100code-quality
Analyzes code quality, complexity, duplication, and architectural patterns. Use after implementing features, during code review, or when preparing for PR. Auto-invoke when user has completed significant code changes or asks to review code quality. - 100code-quality
Provides code quality principles including SOLID, DRY, testing strategies, and best practices for implementation review. Use when reviewing code or applying quality standards. - 100code-quality
Provides code quality principles including SOLID, DRY, testing strategies, and best practices for implementation review. Use when reviewing code or applying quality standards. - 100architecture-patterns
Deep dive into software architecture for macOS. Covers SOLID principles, design patterns, and modular code organization. Use when designing app architecture or refactoring.