code-review

Audit source code for logic errors, race conditions, and resource leaks.

2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/iuliandita/skills --skill code-review-iuliandita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/iuliandita/skills/tree/main/skills/code-review
Command: npx skills add https://github.com/iuliandita/skills --skill code-review-iuliandita

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the gap between static linting and human intuition by identifying logic errors, edge cases, and fragile assumptions that cause production failures.

Core Features & Use Cases

  • Correctness Audit: Evaluates code for logic errors, race conditions, resource leaks, and boundary value issues.
  • Multi-Language Support: Provides targeted checks for TypeScript, Python, Go, Java, Bash, and Infrastructure as Code.
  • Use Case: Before merging a critical PR, use this skill to perform a sanity check on complex logic paths and API boundaries that automated linters typically ignore.

Quick Start

Run a code review on the current directory to identify potential logic bugs and reliability issues.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I find logic errors and race conditions that static analysis ignores?

A correctness audit identifies logic errors, race conditions, and resource leaks by evaluating logic paths, boundary values, and API contracts. It bridges the gap between static linting and human intuition to catch fragile assumptions.

Can I run a pre-merge code review on both TypeScript and Python codebases?

Yes, you can run pre-merge correctness audits on both TypeScript and Python codebases. The audit supports multi-language environments including Go, Java, Bash, and Infrastructure as Code for release sanity checks.

What is the best way to check boundary values and API contracts before a release?

The best way to check boundary values and API contracts before a release is to execute a correctness audit. It systematically evaluates complex logic paths and API boundaries to prevent production failures.

How do I audit Infrastructure as Code for resource leaks and fragile assumptions?

You can audit Infrastructure as Code for resource leaks and fragile assumptions by running a targeted correctness audit. It evaluates edge cases and resource handling across multi-language codebases to ensure reliability.

Does a deep code review replace automated linters for finding edge cases?

A deep code review does not replace automated linters; it addresses the gap between static linting and human intuition. It identifies fragile assumptions and edge cases that automated linters typically ignore.