skills.rest
Mybigwang
MybigwangCOMMUNITY
Explore all skills by this author →
GitHub

review-change

Review code modules or diffs for correctness, maintainability, and risk.

2|Updated Apr 7, 2026
Search Tags:#static analysis#code review#maintainability#test coverage#risk assessment#boundary cases
One-click install
npx skills add https://github.com/Mybigwang/project-agent --skill review-change-mybigwang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-change
Source: https://github.com/Mybigwang/project-agent/tree/main/src/project_agent/skills/builtin/review-change
Command: npx skills add https://github.com/Mybigwang/project-agent --skill review-change-mybigwang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly evaluate a specific module or recent change so that correctness, maintainability, and risk are addressed before the code reaches production.

Core Features & Use Cases

  • Strict, scoped review: Reviews exactly the range you provide (e.g., a file, diff, or section) to keep feedback actionable and not generic.
  • Risk-oriented findings: Flags issues by severity (HIGH / MEDIUM / LOW) across correctness, boundary cases, safety, and test adequacy.
  • Maintainability and complexity checks: Identifies unnecessary complexity and points out opportunities to simplify or harden logic.

Quick Start

Provide the change range to review and ask the agent to perform a strict code audit with severity-ranked findings.

Frequently Asked Questions about review-change

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

FAQPage Schema
How do I perform a code review on a specific file diff for boundary cases and risk?▼

To perform a code review on a file diff, you provide the specific change range to the agent for a strict, scoped review. It evaluates boundary cases and risks, producing severity-labeled issues with file locations.

What is static analysis for maintainability and test coverage adequacy?▼

Static analysis for maintainability and test coverage identifies unnecessary complexity and evaluates whether tests adequately cover the provided code. It flags opportunities to simplify logic and harden safety within a strict review scope.

Can I assess risk and correctness for only a recent code change?▼

Yes, you can assess risk and correctness for a recent code change by requesting a diff-based inspection. The review stays strictly scoped to the range provided, ensuring feedback is actionable and focused on boundary conditions.

Does this code review approach flag issues by severity for safety and correctness?▼

Yes, this code review approach flags issues by severity across correctness, boundary cases, and safety. It categorizes findings as HIGH, MEDIUM, or LOW to help prioritize maintainability fixes and risk mitigation.

What are the limitations of a scoped static analysis for code review?▼

A scoped static analysis for code review limits feedback strictly to the provided file, diff, or section range. It will not evaluate overarching system architecture outside the specified scope, but confirms a clear conclusion when no obvious problems are found.

Related Skills

Explore More Software Engineering Skills→
balic-AI-ML-R-D-Resourcesbalic-AI-ML-R-D-Resources

security-audit-context-building

Map architecture, trust boundaries, and data flows for security audit scoping.

Official
Advanced
ZJU-REALZJU-REAL
195

code-review

Review code changes for security, correctness, performance, and testing issues.

Official
Advanced
buchananwillbuchananwill
2

general-correctness

Assess codebases for specification fidelity and boundary condition handling.

Community
Intermediate
balajivisbalajivis
2

review

Analyze Git-based code diffs to detect structural risks before merging.

Community
Advanced