code-review-validating

Analyze code for logical correctness, edge cases, and error handling issues.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/wizeline/sdlc-agents --skill code-review-validating
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-validating
Source: https://github.com/wizeline/sdlc-agents/tree/main/aicores/code-review-agent/skills/code-review-validating
Command: npx skills add https://github.com/wizeline/sdlc-agents --skill code-review-validating

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill rigorously analyzes code to identify logical correctness and robustness issues, ensuring software functions reliably under all conditions.

Core Features & Use Cases

  • Bug Detection: Finds potential crashes, race conditions, and logic errors.
  • Edge Case Analysis: Systematically checks for vulnerabilities related to null values, empty collections, and boundary conditions.
  • Error Handling Review: Ensures errors are propagated correctly with sufficient context.
  • Use Case: A developer submits a new feature. This Skill is used to proactively find potential bugs and edge cases before they reach production, improving code quality and stability.

Quick Start

Use the code-review-validating skill to find bugs in the file 'user_service.py'.

Frequently Asked Questions about code-review-validating

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

FAQPage Schema
How do I find race conditions and logic errors in my code?

An edge case analysis systematically checks for vulnerabilities related to null values, empty collections, and boundary conditions to ensure software functions reliably under all conditions.

How do I check if errors are propagated correctly with sufficient context?

To check error propagation, a correctness-focused code review analyzes error paths to ensure errors are propagated correctly with sufficient context, preventing silent failures and improving stability.

What is the best way to review code for business rule violations and null handling?

The best way to review code for business rule violations and null handling is a systematic review process that maps behavioral contracts and enumerates edge cases to rigorously identify logical correctness issues.

Does this code review approach work for finding bugs in any programming language?

This code review approach works for finding bugs across programming languages by rigorously analyzing logical correctness and robustness issues independent of specific frameworks or platform dependencies.

When do I need a correctness-focused code review instead of a standard one?

You need a correctness-focused code review when proactively finding potential bugs and edge cases before they reach production, ensuring software functions reliably under all conditions and improving code quality.