revisar-codigo

Reviews diffs, files, and pull requests, reporting findings ordered by severity with file and line.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/GuilhermeBrancalhao/ENGINE-CODEX --skill revisar-codigo-guilhermebrancalhao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: revisar-codigo
Source: https://github.com/GuilhermeBrancalhao/ENGINE-CODEX/tree/main/motores/revisar-codigo
Command: npx skills add https://github.com/GuilhermeBrancalhao/ENGINE-CODEX --skill revisar-codigo-guilhermebrancalhao

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code review often produces vague, unordered feedback that mixes style nitpicks with real defects, forcing the author to do the triage themselves. This Skill performs language-agnostic code review that diagnoses what is wrong, why it breaks, and what the fix is, with every finding located by file and line. ## Core Features & Use Cases - Severity-ordered findings: Reports are sorted into Defect, Risk, Design, and Style categories, and empty categories are stated explicitly rather than padded with invented issues. - Flexible review targets: Reviews pasted code, git diffs and staged changes, named files or directories read in full, and evaluates the resulting code rather than only added lines. - Concrete, verified findings: Each finding cites file and line, names the concrete input that triggers the failure, and proposes one correction, with a false-positive filter applied before reporting. - Use Case: Paste a stack trace or run it against git diff before merging a PR to get an actionable list of correctness, security, concurrency, and testability issues ordered by severity. ## Quick Start Review my current uncommitted changes with git diff and report any defects, risks, or design problems with file and line references.

Frequently Asked Questions about revisar-codigo

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

FAQPage Schema
How do I review a git diff before merging a pull request?▼

Run the review against `git diff` or `git diff --staged`, plus `git log --oneline -5` to understand the change intent. The review evaluates the resulting code, not just added lines, since a removed line may have been the one validating input.

What does a good code review report look like?▼

Findings are ordered by severity: Defect, Risk, Design, then Style. Each finding cites file and line, names the concrete input that triggers the failure, and proposes one correction. Empty severity categories are stated explicitly rather than padded.

Can this review Java or Spring code?▼

Java and JVM targets such as Kotlin, Groovy, Maven, Gradle, JPA entities, or Spring stack traces are delegated to the java-senior skill, which has deeper Spring and JPA criteria. This reviewer handles all other languages.

Why does code review produce false positives?▼

False positives come from reporting defects already guarded elsewhere or without a real triggering input. Each finding passes a verification filter: confirm a reachable input exists, check for validation in callers or middleware, and verify the cited line.

What concurrency issues should a code review check?▼

Key checks include unprotected shared state, divergent lock acquisition ordering, network calls without timeouts, retries on non-idempotent operations, and check-then-use races. Each has a concrete failure condition and a standard correction such as idempotency keys or atomic operations.