skills.rest
rachel353
rachel353COMMUNITY
Explore all skills by this author →
GitHub

code-review-large

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

Updated Apr 7, 2026
Search Tags:#architecture#performance#security#maintainability#code-review#review-report#large-pr
One-click install
npx skills add https://github.com/rachel353/fullty-plan --skill code-review-large-rachel353
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-large
Source: https://github.com/rachel353/fullty-plan/tree/main/.claude/skills/code-review-large
Command: npx skills add https://github.com/rachel353/fullty-plan --skill code-review-large-rachel353

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large PRs can obscure architecture decisions, introduce performance regressions, security gaps, and maintainability issues that are hard to spot in short reviews.

Core Features & Use Cases

  • Architecture and design pattern assessment for large-scale changes.
  • Performance impact analysis and regression spotting.
  • Security vulnerability checks aligned with OWASP Top 10.
  • Maintainability assessment, technical debt identification, and changelog completeness.
  • Use Case: Before merging a big PR, generate a comprehensive report that highlights risk areas and proposed refactors.

Quick Start

Provide a large PR diff to the skill and request a full code-review report.

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 a large pull request exceeding 500 lines?▼

To review a large pull request, you can generate a comprehensive code-review report that surfaces architecture, performance, security, and maintainability issues by providing the PR diff to the skill.

What is the best way to check a big PR for OWASP Top 10 security vulnerabilities?▼

Checking a big PR for OWASP Top 10 security vulnerabilities is done by running a security-focused code review that identifies potential security gaps and risk areas within the provided pull request diff.

Can I assess performance impact and regressions in backend services before merging?▼

You can assess performance impact and spot regressions in backend services by requesting a performance impact analysis on your large PR diff before merging the changes.

How do I identify technical debt and architecture issues in a massive code diff?▼

Identifying technical debt and architecture issues in a massive code diff involves performing an architecture and design pattern assessment to highlight maintainability issues and propose refactors.

Does this code review work for libraries and APIs or only backend services?▼

This code review works for backend services, libraries, and APIs. It applies to any large pull requests exceeding 500 lines across these software engineering contexts before merging.

Related Skills

Explore More Software Engineering Skills→
xrehpicxxrehpicx
4

code-review-change-size

Examine PR diffs to enforce 800-line limits and suggest staged landings.

Community
Intermediate
suhwansuhwan

security-review

Audit codebases for OWASP Top 10 vulnerabilities and hardcoded secrets.

Community
Advanced
JacksonZx535JacksonZx535

ship

Automate software release workflows with Git and GitHub PR creation.

Community
Advanced
mitchellvandusen-cellmitchellvandusen-cell

security-audit

Audit codebases for OWASP Top 10, OAuth, and Flask-specific vulnerabilities.

Community
Advanced