Get the FREE Ultimate OpenClaw Setup Guide →

code-review-large

Scanned
npx machina-cli add skill breaking-brake/cc-wf-studio/code-review-large --openclaw
Files (1)
SKILL.md
548 B

Code Review Large

Overview

Thorough review for large PRs exceeding 500 lines.

Checks

  • Architecture and design patterns
  • Performance implications
  • Security vulnerabilities (OWASP Top 10)
  • Maintainability and technical debt
  • Breaking changes assessment
  • Documentation completeness

Output

  • Comprehensive report with severity ratings and recommendations

Source

git clone https://github.com/breaking-brake/cc-wf-studio/blob/main/.claude/skills/code-review-large/SKILL.mdView on GitHub

Overview

Code Review Large performs a thorough assessment of PRs exceeding 500 lines, focusing on architecture, performance, security, and maintainability. It produces a comprehensive report with severity ratings and actionable recommendations, helping teams catch issues early and reduce risk before merging.

How This Skill Works

The skill analyzes the PR for architectural patterns, design quality, performance implications, security vulnerabilities (aligned to OWASP Top 10), and maintainability and technical debt. It then synthesizes findings into a structured report with severity ratings, prioritized fixes, and actionable mitigations.

When to Use It

  • Before merging large PRs (>500 lines) to catch architecture, performance, and security issues.
  • During critical refactors that touch core modules or APIs.
  • When assessing breaking changes and backward compatibility across services.
  • In projects with strict release governance or compliance requirements.
  • When evaluating technical debt and maintainability in big changes.

Quick Start

  1. Step 1: Identify a large PR (>500 lines) suitable for Code Review Large.
  2. Step 2: Run the Code Review Large analysis to generate the report.
  3. Step 3: Act on severity-based recommendations and update the PR accordingly.

Best Practices

  • Break large changes into smaller PRs whenever feasible to simplify review.
  • Pair architecture, security, and performance reviews for big changes.
  • Ensure documentation, changelogs, and inline comments are complete.
  • Prioritize findings by severity and real-user impact.
  • Use cross-team validation to confirm design patterns and maintainability.

Example Use Cases

  • Refactor of an authentication module spanning 600+ lines with API changes.
  • End-to-end rewrite of a data ingestion pipeline affecting performance and reliability.
  • Database schema migration accompanied by associated code changes.
  • Security controls introduction aligned with the OWASP Top 10.
  • Cross-service API surface changes requiring compatibility checks.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers