ratacat/claude-skills/workflows-review

Arguments

[PR number, GitHub URL, branch name, or latest]

Review Command

<command_purpose> Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and Git worktrees for deep local inspection. </command_purpose>

Introduction

<role>Senior Code Review Architect with expertise in security, performance, architecture, and quality assurance</role>

Prerequisites

<requirements>

• Git repository with GitHub CLI (gh) installed and authenticated
• Clean main/master branch
• Proper permissions to create worktrees and access the repository
• For document reviews: Path to a markdown file or document

</requirements>

Main Tasks

1. Determine Review Target & Setup (ALWAYS FIRST)

<review_target> #$ARGUMENTS </review_target>

<thinking> First, I need to determine the review target type and set up the code for analysis. </thinking>

Immediate Actions:

<task_list>

• [ ] Determine review type: PR number (numeric), GitHub URL, file path (.md), or empty (current branch)
• [ ] Check current git branch
• [ ] If ALREADY on the target branch (PR branch, requested branch name, or the branch already checked out for review) → proceed with analysis on current branch
• [ ] If DIFFERENT branch than the review target → offer to use worktree: "Use git-worktree skill for isolated Call skill: git-worktree with branch name
• [ ] Fetch PR metadata using gh pr view --json for title, body, files, linked issues
• [ ] Set up language-specific analysis tools
• [ ] Prepare security scanning environment
• [ ] Make sure we are on the branch we are reviewing. Use gh pr checkout to switch to the branch or manually checkout the branch.

Ensure that the code is ready for analysis (either in worktree or on current branch). ONLY then proceed to the next step.

</task_list>

Protected Artifacts

<protected_artifacts> The following paths are compound-engineering pipeline artifacts and must never be flagged for deletion, removal, or gitignore by any review agent:

• docs/plans/*.md — Plan files created by /workflows:plan. These are living documents that track implementation progress (checkboxes are checked off by /workflows:work).
• docs/solutions/*.md — Solution documents created during the pipeline.

If a review agent flags any file in these directories for cleanup or removal, discard that finding during synthesis. Do not create a todo for it. </protected_artifacts>

Parallel Agents to review the PR:

<parallel_tasks>

Run ALL or most of these agents at the same time:

1. Task kieran-rails-reviewer(PR content)
2. Task dhh-rails-reviewer(PR title)
3. If turbo is used: Task rails-turbo-expert(PR content)
4. Task git-history-analyzer(PR content)
5. Task dependency-detective(PR content)
6. Task pattern-recognition-specialist(PR content)
7. Task architecture-strategist(PR content)
8. Task code-philosopher(PR content)
9. Task security-sentinel(PR content)
10. Task performance-oracle(PR content)
11. Task devops-harmony-analyst(PR content)
12. Task data-integrity-guardian(PR content)
13. Task agent-native-reviewer(PR content) - Verify new features are agent-accessible

</parallel_tasks>

Conditional Agents (Run if applicable):

<conditional_agents>

These agents are run ONLY when the PR matches specific criteria. Check the PR files list to determine if they apply:

If PR contains database migrations (db/migrate/*.rb files) or data backfills:

1. Task data-migration-expert(PR content) - Validates ID mappings match production, checks for swapped values, verifies rollback safety
2. Task deployment-verification-agent(PR content) - Creates Go/No-Go deployment checklist with SQL verification queries

When to run migration agents:

• PR includes files matching db/migrate/*.rb
• PR modifies columns that store IDs, enums, or mappings
• PR includes data backfill scripts or rake tasks
• PR changes how data is read/written (e.g., changing from FK to string column)
• PR title/body mentions: migration, backfill, data transformation, ID mapping

What these agents check:

• data-migration-expert: Verifies hard-coded mappings match production reality (prevents swapped IDs), checks for orphaned associations, validates dual-write patterns
• deployment-verification-agent: Produces executable pre/post-deploy checklists with SQL queries, rollback procedures, and monitoring plans

</conditional_agents>

4. Ultra-Thinking Deep Dive Phases

<ultrathink_instruction> For each phase below, spend maximum cognitive effort. Think step by step. Consider all angles. Question assumptions. And bring all reviews in a synthesis to the user.</ultrathink_instruction>

<deliverable> Complete system context map with component interactions </deliverable>

Phase 3: Stakeholder Perspective Analysis

<thinking_prompt> ULTRA-THINK: Put yourself in each stakeholder's shoes. What matters to them? What are their pain points? </thinking_prompt>

<stakeholder_perspectives>

1. Developer Perspective <questions>

• How easy is this to understand and modify?
• Are the APIs intuitive?
• Is debugging straightforward?
• Can I test this easily? </questions>

1. Operations Perspective <questions>

• How do I deploy this safely?
• What metrics and logs are available?
• How do I troubleshoot issues?
• What are the resource requirements? </questions>

1. End User Perspective <questions>

• Is the feature intuitive?
• Are error messages helpful?
• Is performance acceptable?
• Does it solve my problem? </questions>

1. Security Team Perspective <questions>

• What's the attack surface?
• Are there compliance requirements?
• How is data protected?
• What are the audit capabilities? </questions>

1. Business Perspective <questions>

• What's the ROI?
• Are there legal/compliance risks?
• How does this affect time-to-market?
• What's the total cost of ownership? </questions> </stakeholder_perspectives>

Phase 4: Scenario Exploration

<thinking_prompt> ULTRA-THINK: Explore edge cases and failure scenarios. What could go wrong? How does the system behave under stress? </thinking_prompt>

<scenario_checklist>

• [ ] Happy Path: Normal operation with valid inputs
• [ ] Invalid Inputs: Null, empty, malformed data
• [ ] Boundary Conditions: Min/max values, empty collections
• [ ] Concurrent Access: Race conditions, deadlocks
• [ ] Scale Testing: 10x, 100x, 1000x normal load
• [ ] Network Issues: Timeouts, partial failures
• [ ] Resource Exhaustion: Memory, disk, connections
• [ ] Security Attacks: Injection, overflow, DoS
• [ ] Data Corruption: Partial writes, inconsistency
• [ ] Cascading Failures: Downstream service issues </scenario_checklist>

6. Multi-Angle Review Perspectives

Technical Excellence Angle

• Code craftsmanship evaluation
• Engineering best practices
• Technical documentation quality
• Tooling and automation assessment

Business Value Angle

• Feature completeness validation
• Performance impact on users
• Cost-benefit analysis
• Time-to-market considerations

Risk Management Angle

• Security risk assessment
• Operational risk evaluation
• Compliance risk verification
• Technical debt accumulation

Team Dynamics Angle

• Code review etiquette
• Knowledge sharing effectiveness
• Collaboration patterns
• Mentoring opportunities

4. Simplification and Minimalism Review

Run the Task code-simplicity-reviewer() to see if we can simplify the code.

5. Findings Synthesis and Todo Creation Using file-todos Skill

<critical_requirement> ALL findings MUST be stored in the todos/ directory using the file-todos skill. Create todo files immediately after synthesis - do NOT present findings for user approval first. Use the skill for structured todo management. </critical_requirement>

Step 1: Synthesize All Findings

<thinking> Consolidate all agent reports into a categorized list of findings. Remove duplicates, prioritize by severity and impact. </thinking>

<synthesis_tasks>

• [ ] Collect findings from all parallel agents
• [ ] Discard any findings that recommend deleting or gitignoring files in docs/plans/ or docs/solutions/ (see Protected Artifacts above)
• [ ] Categorize by type: security, performance, architecture, quality, etc.
• [ ] Assign severity levels: 🔴 CRITICAL (P1), 🟡 IMPORTANT (P2), 🔵 NICE-TO-HAVE (P3)
• [ ] Remove duplicate or overlapping findings
• [ ] Estimate effort for each finding (Small/Medium/Large)

</synthesis_tasks>

Step 2: Create Todo Files Using file-todos Skill

<critical_instruction> Use the file-todos skill to create todo files for ALL findings immediately. Do NOT present findings one-by-one asking for user approval. Create all todo files in parallel using the skill, then summarize results to user. </critical_instruction>

Implementation Options:

Option A: Direct File Creation (Fast)

• Create todo files directly using Write tool
• All findings in parallel for speed
• Use standard template from .claude/skills/file-todos/assets/todo-template.md
• Follow naming convention: {issue_id}-pending-{priority}-{description}.md

Option B: Sub-Agents in Parallel (Recommended for Scale) For large PRs with 15+ findings, use sub-agents to create finding files in parallel:

# Launch multiple finding-creator agents in parallel
Task() - Create todos for first finding
Task() - Create todos for second finding
Task() - Create todos for third finding
etc. for each finding.

Sub-agents can:

• Process multiple findings simultaneously
• Write detailed todo files with all sections filled
• Organize findings by severity
• Create comprehensive Proposed Solutions
• Add acceptance criteria and work logs
• Complete much faster than sequential processing

Execution Strategy:

1. Synthesize all findings into categories (P1/P2/P3)
2. Group findings by severity
3. Launch 3 parallel sub-agents (one per severity level)
4. Each sub-agent creates its batch of todos using the file-todos skill
5. Consolidate results and present summary

Process (Using file-todos Skill):

1. For each finding:

• Determine severity (P1/P2/P3)
• Write detailed Problem Statement and Findings
• Create 2-3 Proposed Solutions with pros/cons/effort/risk
• Estimate effort (Small/Medium/Large)
• Add acceptance criteria and work log

1. Use file-todos skill for structured todo management:

``bash skill: file-todos ``

The skill provides:

• Template location: .claude/skills/file-todos/assets/todo-template.md
• Naming convention: {issue_id}-{status}-{priority}-{description}.md
• YAML frontmatter structure: status, priority, issue_id, tags, dependencies
• All required sections: Problem Statement, Findings, Solutions, etc.

1. Create todo files in parallel:

``bash {next_id}-pending-{priority}-{description}.md ``

1. Examples:

`` 001-pending-p1-path-traversal-vulnerability.md 002-pending-p1-api-response-validation.md 003-pending-p2-concurrency-limit.md 004-pending-p3-unused-parameter.md ``

1. Follow template structure from file-todos skill: .claude/skills/file-todos/assets/todo-template.md

Todo File Structure (from template):

Each todo must include:

• YAML frontmatter: status, priority, issue_id, tags, dependencies
• Problem Statement: What's broken/missing, why it matters
• Findings: Discoveries from agents with evidence/location
• Proposed Solutions: 2-3 options, each with pros/cons/effort/risk
• Recommended Action: (Filled during triage, leave blank initially)
• Technical Details: Affected files, components, database changes
• Acceptance Criteria: Testable checklist items
• Work Log: Dated record with actions and learnings
• Resources: Links to PR, issues, documentation, similar patterns

File naming convention:

{issue_id}-{status}-{priority}-{description}.md