skills.rest
silvio-l
silvio-lCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

code-change-review

Review code changes for regressions, boundary violations, and missing tests.

Updated Aug 23, 2026
Search Tags:#testing#architecture#code review#pull request#maintainability#regressions
One-click install
npx skills add https://github.com/silvio-l/copilot-skills --skill code-change-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-change-review
Source: https://github.com/silvio-l/copilot-skills/tree/main/code-change-review
Command: npx skills add https://github.com/silvio-l/copilot-skills --skill code-change-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a fast, consistent, and structured evaluation of code changes to detect correctness issues, regressions, architectural or boundary violations, missing validations, and maintainability problems before merging.

Core Features & Use Cases

  • Correctness & Regression Detection: Assess whether the change achieves its stated goal and introduces unintended behavioral regressions.
  • Architecture & Boundary Analysis: Identify coupling, boundary violations, and risks to system invariants or interfaces.
  • Maintainability & Testing: Flag missing tests, complex or fragile code, and opportunities to simplify or harden the change.
  • Use Case: Review a pull request that modifies caching and concurrency logic to ensure thread-safety, proper invalidation boundaries, adequate tests, and no performance regressions.

Quick Start

Review the attached pull request diff for functional regressions, architecture boundary violations, missing tests, and provide a concise prioritized list of improvements.

Frequently Asked Questions about code-change-review

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

FAQPage Schema
How do I review a pull request for regressions and architectural boundary violations?▼

Code review for regressions and architectural boundary violations involves analyzing change diffs and surrounding context to detect unintended side effects, coupling risks, and interface threats before merging.

What is the best way to check code changes for maintainability issues and missing test coverage?▼

Checking code changes for maintainability issues and missing test coverage requires evaluating patchsets against test results to flag fragile logic, complexity, and gaps in test validations, yielding a prioritized list of improvements.

Can I use automated code review to assess functional risks in caching and concurrency logic?▼

Automated code review can assess functional risks in caching and concurrency logic by evaluating thread-safety, proper invalidation boundaries, and performance regressions within the provided diffs and surrounding code context.

Does code change analysis work without access to surrounding code context and test results?▼

Code change analysis does not work effectively without access to surrounding code context and test results, because identifying regressions, boundary violations, and maintainability issues relies on understanding the broader system invariants.

Related Skills

Explore More Software Engineering Skills→
ZenkakuHiraganaZenkakuHiragana

code-review

Identify and prioritize defects and maintainability issues in code diffs.

Community
Advanced
alexander-danilenkoalexander-danilenko
14

code-reviewer

Review pull requests and generate prioritized code review reports.

Community
Advanced
aniruddh2003aniruddh2003
1

speckit.checker

Run static analysis tools to detect security vulnerabilities, type errors, and linting issues.

Community
Intermediate
chicanoandres702chicanoandres702

code-reviewer

Automate code reviews to identify security, performance, and reliability issues.

Community
Advanced