review-logic

Identify logic errors and edge cases in code files or directories.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/tvishwanadha/skills --skill review-logic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-logic
Source: https://github.com/tvishwanadha/skills/tree/main/plugins/reviewer/skills/review-logic
Command: npx skills add https://github.com/tvishwanadha/skills --skill review-logic

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Review logic and edge cases in code to detect subtle bugs, improve robustness, and prevent runtime failures.

Core Features & Use Cases

  • Structured logic review for control flow, edge cases, and error handling.
  • Works on single files or whole directories; integrates with the reviewer framework for standardized outputs.
  • Useful for pre-commit checks, PR reviews, and automated audits to catch regressions early.

Quick Start

Provide the target file or directory path to review, and run the orchestrator to obtain findings.

Frequently Asked Questions about review-logic

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

FAQPage Schema
How do I identify logic errors and edge cases in my code?

Identifying logic errors and edge cases involves auditing control flow and error handling to catch subtle bugs. This logic review improves correctness by detecting potential runtime failures using static analysis over individual files or directories.

What is the best way to automate code logic reviews for pull requests?

Automating code logic reviews for pull requests uses diff-based scoping to analyze changes. This catches regressions early by running automated checks that output findings in a standardized format, ensuring robust pre-commit validation without manual inspection.

Can I run an automated logic audit on a whole project directory?

Yes, you can run an automated logic audit on a whole project directory. The review process applies to individual files, directories, or the entire project, loading default rules and local guidance to evaluate code correctness comprehensively.

How does static analysis find edge cases in error handling?

Static analysis finds edge cases in error handling by applying structured rules to examine control flow logic. It reviews how code manages unexpected states, detecting subtle bugs and preventing runtime failures before the code is executed.

Do I need specific dependencies to perform a diff-based code review?

No specific dependencies are required to perform a diff-based code review. The process integrates with an orchestrator to scope reviews to code changes and loads default rules automatically, merging any available local guidance during the analysis.