code-review

Review code or diffs for logic errors, security risks, and bad practices.

1|Updated May 11, 2026
One-click install
npx skills add https://github.com/skalanux/puntofiles --skill code-review-skalanux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/skalanux/puntofiles/tree/main/dot_agents/skills/code-review
Command: npx skills add https://github.com/skalanux/puntofiles --skill code-review-skalanux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you catch logic errors, bad practices, and security vulnerabilities early by performing a consistent first-pass review of code or diffs before deeper, language-specific analysis.

Core Features & Use Cases

  • Language-agnostic first-pass review: Surfaces cross-cutting issues like ordering bugs, magic strings, weak error handling, and unsafe input usage.
  • Structured, severity-based findings: Reports results grouped into critical, high, medium, and low so you can triage quickly.
  • Flexible input handling: Reviews a single file, a multi-hunk diff, or (when needed) explores the repo just enough to resolve external references.

Quick Start

Share the code you'd like reviewed — paste it directly, upload a file, or provide a git diff.

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 security risks in a git diff?

A language-agnostic code review detects logic errors and security risks in a git diff by checking for operation ordering issues, unsafe input usage, and SQL injection patterns. It outputs structured findings with locations, severities, and actionable fixes.

What is a first-pass code review and when do I need it?

A first-pass code review is an early audit of code or multi-hunk diffs to catch bad practices, weak error handling, and maintainability issues. You need it before deeper, language-specific analysis to triage critical vulnerabilities quickly.

How do I check my code for SQL injection and maintainability issues?

To check code for SQL injection and maintainability issues, perform a fast audit using a language-agnostic review pass. It surfaces strict type checking concerns, magic values, and bad practices, grouping results by severity for quick triage.

Can I review a multi-hunk diff without specifying a programming language?

Yes, you can review a multi-hunk diff without specifying a programming language. The review applies language-agnostic passes to identify cross-cutting issues like magic strings and weak error handling, producing structured, severity-based findings.

Does the code review provide specific locations and fixes for detected issues?

Yes, the code review provides specific locations and actionable fixes for detected issues. It produces structured findings that detail the exact review pass, severity level, and concrete solutions for logic errors and security vulnerabilities.

What's the best way to audit code diffs for bad practices and operation ordering issues?

The best way to audit code diffs for bad practices and operation ordering issues is to apply a consistent first-pass review. This approach surfaces cross-cutting reliability concerns and strict type checking issues early, grouped by severity for efficient triage.