general-code-review

Automate code-review of diffs for correctness, simplicity, and test coverage.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps backpressure agents quickly identify defects, unnecessary complexity, and gaps in test coverage when reviewing diffs, reducing manual review time and increasing reliability.

Core Features & Use Cases

  • Correctness & clarity: detects logical errors, edge cases, and unclear intent in changes.
  • Simplicity & reuse: flags unnecessary complexity and opportunities for refactoring or reuse.
  • Test quality evaluation: assesses test coverage, asserts robustness, and surfaces missing tests.
  • Use Case: When evaluating a code change, run this skill to surface defects and propose concrete improvements before integration.

Quick Start

Provide a diff for review and receive a structured critique with actionable fixes.

Frequently Asked Questions about general-code-review

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

FAQPage Schema
How do I automate code review for correctness and test coverage on a pull request?

Automated code review evaluates per-iteration diffs against tests, lint results, and established reviewer standards to detect logical errors, edge cases, and missing test coverage before integration.

What is the best way to review a diff for unnecessary complexity and reuse opportunities?

Reviewing a diff for simplicity and reuse flags unnecessary complexity and surfaces concrete refactoring opportunities, focusing on established reviewer standards rather than type-design decisions.

How does automated static analysis evaluate test quality gaps in a code change?

Automated static analysis evaluates test quality by assessing test coverage, checking assert robustness, and surfacing missing tests within the provided diff to propose concrete improvements.

Can I use this automated code review skill without configuring external dependencies?

Yes, this automated code review skill operates without external dependencies, requiring only a provided diff to generate a structured critique with actionable, prioritized fixes.

When should I not use automated diff review for type-design decisions?

Avoid using automated diff review for type-design decisions, as the evaluation specifically focuses on correctness, reuse, test-quality gaps, and simplicity rather than architectural type choices.

How do I get prioritized fixes for logical errors and edge cases found during code review?

To get prioritized fixes for logical errors, provide a diff for review to receive a structured critique that outputs concrete findings with actionable, prioritized fixes against established standards.