rugged-gemini: Skill for Gemini CLI

Code Review Skill

Systematically review against full rule set. Catches what linters miss: arch violations, missing observability, logic errors, pattern inconsistencies.

When to Invoke

• Audit workflows (Phase 1: Code Review)
• User-requested review
• Best: fresh conversation (avoid confirmation bias)

Review Process

1. Scope

• Feature review — all files in feature dir
• PR review — changed files only
• Full audit — all features

2. Load Rules

Apply rules from GEMINI.md. Use Rule Priority (§ Rule Priority) for severity.

3. Categories (Priority Order)

Critical (Must Fix):

• [SEC] Security — injection, hardcoded secrets, broken auth
• [DATA] Data integrity — missing error handling on writes, no transactions
• [RES] Resource leaks — unclosed connections, missing cleanup

Major (Should Fix):

• [TEST] Testability — I/O not behind interfaces, untested error paths
• [OBS] Observability — missing logging, no correlation IDs
• [ERR] Error handling — empty catch, swallowed errors
• [ARCH] Architecture — circular deps, wrong layer access

Minor (Nice to Fix):

• [PAT] Pattern consistency — deviation from codebase patterns
• Naming — unclear names
• Organization — fns too long, mixed responsibilities

Nit: style (linter catches), missing comments on complex logic.

4. Findings Output

# Code Review: {Feature/Module Name}
Date: {date}
Reviewer: AI Agent (fresh context)

## Summary
- **Files reviewed:** N
- **Issues found:** N (X critical, Y major, Z minor, W nit)

## Critical Issues
- [ ] **[SEC]** {description} — [{file}:{line}](file:///path)
- [ ] **[DATA]** {description} — [{file}:{line}](file:///path)

## Major Issues
- [ ] **[TEST]** {description} — [{file}:{line}](file:///path)
- [ ] **[OBS]** {description} — [{file}:{line}](file:///path)

## Minor Issues
- [ ] **[PAT]** {description} — [{file}:{line}](file:///path)

## Nit
- [ ] {description} — [{file}:{line}](file:///path)

## Rules Applied
List of rules referenced.