code-review

Review local diffs, branches, and patches for prioritized correctness, regression, and maintainability risks.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill code-review-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/code-review
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill code-review-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Code changes often ship with hidden bugs, missing tests, and structural regressions that manual review misses. This Skill performs a neutral, evidence-based review of local diffs, branches, files, modules, or patches, producing a prioritized findings ledger and optionally fixing only safe, in-scope findings with focused proof. ## Core Features & Use Cases - Findings-first review: Audits changed code for bugs, regressions, test gaps, reliability and security-adjacent risks, and structural quality issues, classified by P0-P3 severity with stable finding IDs. - Safe scoped remediation: In direct standalone runs, fixes only findings classified Auto-fix: Safe, proving each fix with a red-before/green-after focused regression test; nested or report-only invocations never edit files. - Focused validation protocol: Reruns finding-specific proofs, narrow repository-native tests, scoped lint/type checks, and git diff --check, leaving no caches or generated artifacts behind. - Use Case: Before merging a feature branch, run a review of the current diff to receive a prioritized ledger of a likely race condition (P1, gated), a missing edge-case test (P1, safe and auto-fixed with a failing-then-passing regression test), and a decomposition suggestion for a file crossing 1000 lines. ## Quick Start Use the code-review skill to review the current local branch diff, fix only safe in-scope findings, and report the prioritized findings ledger.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review a local git diff for bugs before merging?

Invoke the code-review skill against your current branch or diff. It maps the changed surface, applies a severity rubric from P0 to Nit, and returns a prioritized findings ledger with evidence, impact, and the smallest remediation for each finding.

What is the difference between code-review and review-pr?

code-review handles local diffs, branches, files, modules, and patches with findings-first analysis. review-pr handles GitHub pull requests by number, URL, or branch, including checkout, conflict repair, checks, and merge readiness.

Can code-review automatically fix the issues it finds?

Only in a direct standalone invocation, and only for findings classified Auto-fix: Safe. Each fix requires a focused regression test proven to fail before the change and pass after; gated findings are reported but never edited.

Does code-review modify files when invoked implicitly or by another workflow?

No. Implicit selection, quoted mentions, and nested use by parent workflows such as align are always report-only. Ambiguous invocation intent fails closed to report-only, and validation leaves no caches or generated artifacts.

When should I not use code-review?

Do not use it for GitHub PR management (use review-pr), project-wide repair across tests, docs, and CI (use align), dedicated security scans or threat modeling (use apply-security), or design-phase architecture decisions (use system-design-rules).