skills.rest
SebKay
SebKayCOMMUNITY
Explore all skills by this author →
Website𝕏@SebKayDesignGitHub

review-code

Review code changes for correctness, regressions, maintainability, and test coverage.

1|Updated Feb 27, 2026
Search Tags:#testing#quality assurance#code review#debugging#refactoring#software development
One-click install
npx skills add https://github.com/SebKay/skills --skill review-code-sebkay
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/SebKay/skills/tree/main/review-code
Command: npx skills add https://github.com/SebKay/skills --skill review-code-sebkay

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps ensure code quality by systematically reviewing code changes for correctness, potential regressions, maintainability issues, and adequate test coverage.

Core Features & Use Cases

  • Code Correctness: Identifies logical errors, unreachable code, and missing states.
  • Regression Detection: Flags potential issues that might break existing functionality.
  • Maintainability Analysis: Points out areas with excessive complexity or repetition that could be refactored.
  • Test Coverage Check: Assesses whether tests adequately cover critical and risky code paths.
  • Use Case: Before merging a pull request, use this Skill to get a detailed analysis of potential issues and areas for improvement.

Quick Start

Review the provided code diff for any potential issues and suggest improvements.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I review code changes for correctness and regressions before a merge?▼

Reviewing code changes for correctness and regressions involves analyzing diffs to identify logical errors, unreachable code, and missing states that might break existing functionality before merging a pull request.

What's the best way to check test coverage for risky code paths in a pull request?▼

Checking test coverage in a pull request requires assessing whether tests adequately cover critical and risky code paths, identifying missing tests, and prioritizing actionable feedback based on evidence.

Can I use automated code review to find maintainability issues and refactoring opportunities?▼

Automated code review can find maintainability issues by pointing out areas with excessive complexity or repetition that could be refactored, ensuring long-term code quality.

How does code review handle regression detection in feature diffs?▼

Regression detection in feature diffs flags potential issues that might break existing functionality by systematically analyzing code changes for defects, risks, and missing states.

Does this code review approach work for refactors and feature updates?▼

This code review approach is applicable to features, pull requests, diffs, and refactors, providing a detailed analysis of potential issues and areas for improvement.

What limitations exist when reviewing code changes for missing tests and defects?▼

Limitations when reviewing code changes include relying on available evidence to identify defects, risks, and missing tests, meaning undocumented or untested external dependencies may go undetected.

Related Skills

Explore More Software Engineering Skills→
aleen42aleen42
3

code-review

Identify defects, regressions, risks, and missing tests in code changes.

Community
Intermediate
LaunchPadLabLaunchPadLab
1

code-review

Review Rails code with Brakeman, Bundler Audit, and RuboCop.

Official
Intermediate
nktfh100nktfh100
1

test-master

Generates test plans, mocking strategies, and defect reports for software projects.

Community
Intermediate
zhaozengqing4364-bitzhaozengqing4364-bit

autopilot

Automates end-to-end software development tasks including planning, coding, and review for CI/CD pipelines.

Community
Advanced