skills.rest
gigaverse-app
gigaverse-appOFFICIAL
Explore all skills by this author →
Website𝕏@dannyandersGitHub

code-review

This is a sample value.

4|Updated Jan 16, 2026
Search Tags:#architecture#patterns#quality#diff#code-review#pull-request
One-click install
npx skills add https://github.com/gigaverse-app/skillet --skill code-review-gigaverse-app
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/gigaverse-app/skillet/tree/main/python-standards/skills/code-review
Command: npx skills add https://github.com/gigaverse-app/skillet --skill code-review-gigaverse-app

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires llm, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps reviewers surface egregious, architecture-oriented issues by focusing on cross-file patterns, maintainability, and code quality rather than just line-by-line checks.

Core Features & Use Cases

  • Cross-file pattern detection: Identify duplicated logic, architectural smells, and inconsistencies across files.
  • Quality-focused review workflow: Prioritize structural issues such as god functions, weak types, and missing interfaces.
  • Large-diff handling guidance: Provides steps to retain context in large PR diffs and apply a scalable review approach.

Quick Start

Diff the current branch against main while excluding noise like lock files to produce a focused PR diff.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I find cross-file code issues in a pull request?▼

To handle large diffs in code reviews, exclude noise like lock files to produce a focused PR diff. This retains context and enables a scalable approach to surface egregious architecture-oriented issues.

What cross-file patterns should I look for during a code review?▼

To handle large diffs in code reviews, exclude noise like lock files to produce a focused PR diff. This retains context and enables a scalable approach to surface egregious architecture-oriented issues.

How do I handle large diffs when reviewing a pull request?▼

Yes, you can prioritize structural code quality over line-by-line checks by enforcing a review mindset that targets egregious issues, cross-file patterns, and architectural smells to improve production code.

Can I prioritize structural code quality over line-by-line checks?▼

To find cross-file code issues in a pull request, analyze diffs across files to surface duplicated logic, architectural smells, and inconsistencies. This approach prioritizes structural integrity over line-by-line checks.

Does analyzing PR diffs work for discovering architectural smells?▼

During a code review, look for cross-file patterns like duplicated logic, architectural smells, god functions, weak types, and missing interfaces. Identifying these structural issues improves overall maintainability.

Related Skills

Explore More Software Engineering Skills→
JonnyCBBJonnyCBB

pr-description

Generate structured PR descriptions from git diffs for GitHub flows.

Community
Advanced
selfagencyselfagency

refactor

Refactor code in small, test-backed steps to preserve behavior.

Community
Intermediate
CaptainPhantasyCaptainPhantasy

dry-logic-unifier

Identify duplicated logic patterns and extract them into shared utility packages.

Community
Intermediate
mkusakamkusaka
7

code-review-correctness-finder-angles

Analyze diff files for line-by-line correctness and cross-file dependencies.

Community
Advanced