correctness-reviewer

Name: correctness-reviewer
Availability: InStock
Author: Udecode

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

434|33|Updated Jul 27, 2025

Search Tags:#debugging #edge-cases #static-analysis #software-quality #code-review #correctness

Ready to run

npx skills add https://github.com/udecode/kitcn --skill correctness-reviewer-udecode

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: correctness-reviewer
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/correctness-reviewer
Command: npx skills add https://github.com/udecode/kitcn --skill correctness-reviewer-udecode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Always-on code-review persona that helps teams catch logic errors, edge cases, state-management bugs, and faulty error propagation before code reaches production.

Core Features & Use Cases

Mentally execute code across branches to trace inputs and state changes, identifying off-by-one and boundary issues.
Detect null/undefined propagation, race conditions, invalid state transitions, and swallowed or misrepresented errors.
Provide actionable review findings with concrete reproduction steps and suggested fixes for PRs, tutorials, or code audits.

Quick Start

Review a given code snippet and generate a concise, targeted correctness report with recommended fixes and repro steps.

Frequently Asked Questions about correctness-reviewer

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

FAQPage Schema

How do I catch logic errors and edge cases before code reaches production?▼

To catch logic errors and edge cases before production, review code to mentally execute branches, trace state changes, and identify off-by-one or boundary issues. This generates a targeted correctness report with concrete reproduction steps and suggested fixes.

What is the best way to detect race conditions and invalid state transitions in async operations?▼

Detecting race conditions and invalid state transitions in async operations requires tracing asynchronous flows to identify faulty error propagation and swallowed errors. The review process generates actionable findings with suggested fixes addressing the root causes of these state-management bugs.

How do I review code for null and undefined propagation issues?▼

Reviewing code for null and undefined propagation involves tracing inputs through code branches to detect invalid state transitions and misrepresented errors. The output provides concrete reproduction steps and root-cause fixes to ensure robust behavior across typical scenarios.

Can I use static analysis to find off-by-one errors in loops?▼

Static analysis can find off-by-one errors in loops by mentally executing the code across branches to trace inputs and boundary issues. The review applies this to typical scenarios like loops and async operations, yielding a concise correctness report with recommended fixes.

Does code review work for auditing error handling and faulty error propagation?▼

Code review works for auditing error handling by detecting swallowed or misrepresented errors and faulty error propagation. It applies review logic to typical scenarios to ensure robust behavior, providing actionable findings with concrete reproduction steps and suggested fixes for root causes.