code-review-large

Analyze large pull requests for architecture, performance, security, and maintainability issues.

5.3k|573|Updated Nov 1, 2025

Search Tags:#architecture #performance #security #maintainability #code-review #large-pr

Ready to run

npx skills add https://github.com/breaking-brake/cc-wf-studio --skill code-review-large-breaking-brake

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-large
Source: https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/code-review-large
Command: npx skills add https://github.com/breaking-brake/cc-wf-studio --skill code-review-large-breaking-brake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In-depth analysis of large pull requests (>500 lines) to surface architecture, performance, security, and maintainability issues early.

Core Features & Use Cases

Architecture and design assessment
Performance impact analysis
Security vulnerability identification (OWASP Top 10)
Maintainability evaluation and technical debt awareness
Breaking changes assessment
Comprehensive, structured report with severity ratings and actionable recommendations

Quick Start

Request a comprehensive review of the latest large PR (>500 lines) covering architecture, performance, security, and maintainability.

Frequently Asked Questions about code-review-large

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review large pull requests for architecture and security issues?▼

To review large pull requests effectively, you need an in-depth analysis that surfaces architecture, performance, security, and maintainability issues early. This process evaluates complex code changes to produce a structured, severity-rated report with actionable recommendations.

What is the best way to assess performance impact and technical debt in a massive code change?▼

Assessing performance impact and technical debt in a massive code change involves evaluating maintainability and identifying security vulnerabilities like the OWASP Top 10. This approach generates a comprehensive report with severity ratings and concrete follow-up tasks.

Can I analyze breaking changes and maintainability across any language stack?▼

Yes, you can assess breaking changes and maintainability across any language stack. The analysis applies to complex code changes regardless of the technology, guiding developers through design, risk, and maintainability considerations.

When do I need a comprehensive code review for maintainability and vulnerabilities?▼

You need a comprehensive code review for maintainability and vulnerabilities when handling large pull requests exceeding 500 lines. This ensures early identification of performance bottlenecks, architecture flaws, and security risks before merging complex changes.

Does large-PR code review work with OWASP Top 10 security vulnerability identification?▼

Yes, large-PR code review includes security vulnerability identification based on the OWASP Top 10. It analyzes extensive code changes to detect security flaws, assess design risks, and provide concrete recommendations to resolve them.