skills.rest
1024XEngineer
1024XEngineerOFFICIAL
Explore all skills by this author →
𝕏@techcamp1024GitHub

review

Review code changes for correctness, regressions, and missing tests.

43|6|Updated Mar 16, 2026
Search Tags:#development#analysis#quality#code-review#pull-request#tests#regressions
One-click install
npx skills add https://github.com/1024XEngineer/bytemind --skill review-1024xengineer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/1024XEngineer/bytemind/tree/main/internal/skills/review
Command: npx skills add https://github.com/1024XEngineer/bytemind --skill review-1024xengineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review helps teams ensure correctness, reduces regressions, and improves testing quality.

Core Features & Use Cases

  • Identify correctness issues and edge cases in code changes.
  • Assess test coverage gaps and verify alignment with changes.
  • Provide structured, severity-ranked findings and actionable recommendations.

Quick Start

Review the latest patch or pull request and produce a prioritized findings report.

Frequently Asked Questions about review

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

FAQPage Schema
How do I perform a code review for correctness and regressions?▼

To perform a code review, analyze the latest patch or pull request to assess correctness, regressions, and missing tests. The process scopes modified files and affected modules, producing a structured report with severity-ranked findings and actionable recommendations.

What is the best way to identify missing test coverage in a pull request?▼

Identifying missing test coverage involves assessing test coverage gaps and verifying alignment with code changes. The review scopes modified files and affected modules, reporting findings by severity with precise locations to highlight areas needing future test coverage updates.

Can I scope code reviews to only the modified files and affected modules?▼

Yes, you can scope code reviews to modified files and affected modules. This ensures the analysis targets code changes for correctness and regressions, providing structured findings and verification steps suitable for PR reviews without evaluating the entire codebase.

How does a code review report format findings for pull requests?▼

A code review report formats findings by severity with precise locations. It provides structured, severity-ranked findings, risks, and verification steps suitable for PR reviews, ensuring teams can prioritize addressing correctness issues and test coverage gaps effectively.

Why do I need to verify test alignment when reviewing code changes?▼

Verifying test alignment ensures that test coverage adequately matches code changes, reducing regressions and improving testing quality. The review assesses test coverage gaps and provides actionable recommendations to maintain correctness across modified files and affected modules.

Related Skills

Explore More Software Engineering Skills→
edlngedlng
2

review-addressed-comments

Verify reviewer feedback is addressed in pull request code.

Community
Intermediate
erikhazzarderikhazzard
1

optimizing-node-backend

Audit Node.js backend code for performance bottlenecks and concurrency failure modes.

Community
Advanced
thesaifalitaithesaifalitai
8

test-master

Write and execute software tests for functionality, performance, and security.

Community
Advanced
awinogradovawinogradov
5

pr:monitor

Monitor pull requests for review approval and CI check status.

Community
Intermediate