code-review

Name: code-review
Availability: InStock
Author: revan710517539

Analyze code changes to identify defects, regressions, and test coverage gaps.

Updated Aug 27, 2026

Search Tags:#risk-assessment #quality-assurance #code-review #pull-request #development-workflow #bug-detection #diff-analysis

Ready to run

npx skills add https://github.com/revan710517539/SuperTeams --skill code-review-revan710517539

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/revan710517539/SuperTeams/tree/main/skills/code-review
Command: npx skills add https://github.com/revan710517539/SuperTeams --skill code-review-revan710517539

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews code changes and reports findings with a risk-first engineering mindset.

Core Features & Use Cases

Prioritize correctness, regressions, and missing coverage
Reference exact file path and line numbers when possible
Integrate into code review workflows to surface high-risk areas

Quick Start

Provide the code changes (diff or patch) and I will review them with a risk-first mindset.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I review a pull request to identify high-risk code changes?▼

To review a pull request with a risk-first mindset, provide the code diff or patch. The analysis prioritizes correctness, regressions, and missing test coverage, referencing exact file paths and line numbers to surface critical paths and potential side effects.

What is a risk-first code review approach for software engineering?▼

A risk-first code review approach evaluates code changes by prioritizing the detection of defects, regressions, and gaps in test coverage. It focuses analysis on risk-prone areas and critical paths to ensure correctness and prevent potential side effects in software projects.

Can I use automated code review to detect missing test coverage in commits?▼

Yes, automated code review can detect missing test coverage in commits. By analyzing provided diffs or patches, the review identifies gaps in coverage alongside correctness issues and potential regressions across software projects.

How do I analyze code diffs for potential regressions and side effects?▼

To analyze code diffs for regressions and side effects, submit the patch for review. The analysis applies a risk-first engineering mindset to identify defects, missing tests, and potential side effects, referencing exact file paths and line numbers when possible.

Does this code review workflow work with any software project's git diff?▼

Yes, this code review workflow works with any software project's git diff. It requires no dependencies and can be integrated into existing development workflows to analyze pull requests and commits across various software projects.

When do I need a risk-first code review for my development workflow?▼

You need a risk-first code review when integrating pull requests or commits into your development workflow and wanting to surface high-risk areas. It focuses on detecting correctness issues, regressions, and missing coverage before changes are merged.