code-review

Analyze pull-request diffs to identify security, performance, quality, and test risks.

2|Updated Sep 13, 2025
One-click install
npx skills add https://github.com/s977043/river-reviewer --skill code-review-s977043
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/s977043/river-reviewer/tree/main/skills/agent-skills/code-review
Command: npx skills add https://github.com/s977043/river-reviewer --skill code-review-s977043

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the review of pull request diffs, identifying security, performance, quality, and test gaps to ensure changes are safe and maintainable.

Core Features & Use Cases

  • Change-aware review: Analyzes diffs to surface high-risk files and actionable fixes.
  • Perspective-specific checks: Security, performance, quality, and tests are evaluated with concrete guidance.
  • Use Case: Applying this to a PR with a large refactor surfaces missing tests and potential security concerns.

Quick Start

Provide the diff of the PR to the skill and receive prioritized feedback and suggested patches.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate security and quality checks on pull request diffs?

Automated PR review analyzes diffs to identify security, performance, quality, and test gaps before merging. Provide the PR diff to surface high-risk changes, missing test coverage, and actionable remediation with severity-based triage and structured feedback integrated into your code-review workflow.

What security risks does static analysis catch in code changes?

Static analysis of diffs detects critical security vulnerabilities, performance bottlenecks, and maintainability issues in pull requests. It flags risky patterns, missing safeguards, and coverage gaps with concrete guidance and suggested patches to remediate before merge.

Can I use diff analysis to identify missing test coverage in large refactors?

Yes. Diff-based review evaluates test coverage across refactored code and surfaces gaps where tests don't validate new or modified logic. It prioritizes coverage deficiencies by severity and provides actionable opportunities to strengthen test suites alongside code changes.

How does PR review automation reduce manual code review overhead?

Automated review pre-screens diffs for security, performance, quality, and test risks, surfacing critical issues and fixes upfront. This triage lets reviewers focus on architecture and business logic, not routine checks, integrating prioritized feedback into existing workflows.

What's the best way to enforce consistent code quality standards across repositories?

Apply perspective-specific checks—security, performance, quality, tests—across PRs uniformly to enforce standards. Severity-based triage and structured feedback with remediation paths ensure consistency and surface gaps that prevent regressions across codebases.