skills.rest
vndkubi
vndkubiCOMMUNITY
Explore all skills by this author →
GitHub

review-code-changes

Analyze code changes to produce per-file review reports with severity ratings.

Updated Mar 4, 2026
Search Tags:#maintainability#code-review#severity#pull-request#tests#per-file
One-click install
npx skills add https://github.com/vndkubi/bootstrap-toolkits --skill review-code-changes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-code-changes
Source: https://github.com/vndkubi/bootstrap-toolkits/tree/main/.github/skills/review-code-changes
Command: npx skills add https://github.com/vndkubi/bootstrap-toolkits --skill review-code-changes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, repeatable process for reviewing code changes across PRs and branches, ensuring business logic correctness, maintainability, and test coverage before merge.

Core Features & Use Cases

  • Trace and validate changes: systematically assess each changed file for logic, tests, and potential regressions.
  • Structured feedback: generate per-file issues with severity and actionable suggestions.
  • Pre-merge quality checks: produce a concise approval recommendation with a merged-ready report.

Quick Start

Run a review on the target PR or branch to generate a structured report for stakeholders.

Frequently Asked Questions about review-code-changes

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

FAQPage Schema
How do I get a structured code review for a pull request before merge?▼

A structured code review for a pull request analyzes branch diffs to produce a per-file report with severity-rated comments, maintainability guidance, and test-coverage notes to ensure merge readiness.

Can I generate a per-file issues table with severity ratings for my branch diff?▼

Yes, analyzing a branch diff generates a per-file issues table that includes severity ratings and actionable suggestions to systematically validate business logic and potential regressions.

What is the best way to check test coverage and maintainability in code changes?▼

Checking test coverage and maintainability in code changes involves systematically assessing each changed file to produce structured feedback and an overall approval recommendation.

Does this code review process provide an overall approval recommendation for stakeholders?▼

Yes, the code review process provides a concise overall approval recommendation alongside a detailed per-file issues table, ensuring consistent quality checks across modules for stakeholders.

How do I systematically trace and validate logic changes across multiple files?▼

To systematically trace and validate logic changes, apply a disciplined workflow to pull requests and branch diffs, generating a structured report that highlights potential regressions and suggested actions.

When do I need a structured pre-merge quality check for my code?▼

A structured pre-merge quality check is needed when you want to ensure business logic correctness, maintainability, and test coverage across PRs and branches before merging into the main codebase.

Related Skills

Explore More Software Engineering Skills→
reedomreedom

collect-commits-and-files

Collect and categorize changed files from Git for review workflows.

Community
Advanced
lpjhelderlpjhelder

code-review

Review code changes for security, quality, and maintainability issues.

Community
Intermediate
birgitta410birgitta410
15

sensors_wrap-tool

Convert command-line tool output into sensors-cli JSON schema.

Community
Intermediate
AIDotNetAIDotNet
84

code-review

Analyze code for bugs, security vulnerabilities, and code smells.

Official
Intermediate