skills.rest
xinbenlv
xinbenlvCOMMUNITY
Explore all skills by this author →
Website𝕏@ZainanZhouGitHub

codereview-correctness

Analyze code diffs for logic bugs and improper error handling.

8|Updated Jan 14, 2026
Search Tags:#edge-cases#null-safety#error-handling#code-review#analyze#race-conditions#logic-bug
One-click install
npx skills add https://github.com/xinbenlv/codereview-skills --skill codereview-correctness
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codereview-correctness
Source: https://github.com/xinbenlv/codereview-skills/tree/main/skills/codereview-correctness
Command: npx skills add https://github.com/xinbenlv/codereview-skills --skill codereview-correctness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reviewers detect logic bugs, edge-case failures, and improper error handling in code changes, reducing production incidents.

Core Features & Use Cases

  • Logic Bug Detection: Identify off-by-one errors, null dereferences, and incorrect error paths.
  • Edge Case Analysis: Reveal unhandled scenarios and risky execution paths.
  • Error Path Verification: Ensure errors are propagated and handled robustly across modules.
  • Use Case: During a PR review, it analyzes the diff to surface the highest-risk areas and suggest targeted fixes.

Quick Start

Use the codereview-correctness skill during a code review to surface logic bugs and suggested fixes in the PR.

Frequently Asked Questions about codereview-correctness

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

FAQPage Schema
How do I find logic bugs and off-by-one errors during a pull request code review?▼

To find logic bugs during a code review, analyze the pull request diff to detect off-by-one errors, null dereferences, and incorrect error paths in core business logic and complex algorithms. This process surfaces risky execution paths and suggests targeted fixes.

What is the best way to check for race conditions and unhandled edge cases in core business logic?▼

Checking for race conditions and unhandled edge cases involves analyzing code changes to reveal risky execution paths and verify robust error propagation. This edge case analysis identifies null handling failures and incorrect error paths across modules before deployment.

How do I verify error handling and error propagation paths across modules in a PR?▼

Verifying error handling paths requires analyzing the code diff to ensure errors are propagated and handled robustly across modules. This error path verification detects incorrect error paths and improper handling within core business logic during the review.

Can I use this code review tool to analyze complex algorithms across different programming languages?▼

Yes, you can analyze complex algorithms across languages during code reviews. The detection mechanism applies to core business logic regardless of language, identifying logic bugs, null handling issues, and race conditions within the submitted changes.

What types of logic bugs can be detected by analyzing a pull request diff?▼

Analyzing a pull request diff can detect logic bugs such as off-by-one errors, null dereferences, race conditions, and incorrect error paths. It surfaces the highest-risk areas in core business logic and complex algorithms to suggest targeted fixes.

Related Skills

Explore More Software Engineering Skills→
sakamoto-family-smilesakamoto-family-smile

code-helper

Analyze code diffs and generate review suggestions and debugging fixes.

Community
Basic
udecodeudecode
434

correctness-reviewer

Identify logic errors, edge cases, and state-management bugs in code.

Official
Advanced
zajcazajca
2

go-linting

Configure golangci-lint with recommended Go linters for static analysis.

Community
Basic
reececoakes99reececoakes99

business-logic-auditor

Identify business logic flaws in web application APIs.

Community
Advanced