code-review-excellence

Review code diffs for correctness, security, regressions, and test coverage with actionable findings.

1|Updated Aug 7, 2025
One-click install
npx skills add https://github.com/zzafergok/arktos --skill code-review-excellence-zzafergok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-excellence
Source: https://github.com/zzafergok/arktos/tree/main/.agent/skills/code-review-excellence
Command: npx skills add https://github.com/zzafergok/arktos --skill code-review-excellence-zzafergok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss critical defects, drown important findings in style nitpicks, or produce vague feedback that authors cannot act on. This Skill structures the review process so every material issue in a pull request, diff, or patch is identified, located, and explained with a concrete remediation path. ## Core Features & Use Cases - Prioritized Review Order: Systematically checks correctness, security and privacy, regression risk, reliability and operations, performance, maintainability, and test coverage in that sequence. - Structured Finding Format: Each issue reports severity, precise file location, triggering condition, likely consequence, why existing safeguards fail, and a focused fix direction. - Feedback Evaluation: Verifies claims from other reviewers against the actual code and tests, accepting sound feedback and challenging incorrect assumptions with evidence. - Use Case: A developer opens a pull request modifying authentication middleware. The Skill inspects the diff and surrounding call sites, flags a missing rate-limit check on a new endpoint as a high-severity security finding, and notes that no test covers the failure path. ## Quick Start Review the changes in this pull request and report any correctness, security, or regression issues with severity and suggested fixes.

Frequently Asked Questions about code-review-excellence

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

FAQPage Schema
How do I review a pull request for security issues?▼

Examine the diff for authorization gaps, missing input validation, injection risks, exposed secrets, and unsafe defaults at trust boundaries. Check each changed endpoint or data flow against the surrounding code to confirm existing safeguards actually cover the new behavior.

What should a good code review finding include?▼

A useful finding states severity proportional to impact, the precise file and location, the triggering condition, the likely consequence, why existing safeguards do not prevent it, and a focused remediation direction. Keep one issue per finding.

How to evaluate code review feedback from another reviewer?▼

Verify each claim directly against the code and tests before responding. Accept feedback that holds up, challenge incorrect assumptions with concrete evidence, and ask for clarification when the desired behavior is ambiguous rather than agreeing performatively.

Does a passing build or lint run prove code is correct?▼

No. A clean build or lint run only confirms syntax and style rules, not behavioral correctness. Meaningful verification requires checking changed behavior and important failure paths with tests or proportionate read-only checks.

When should performance issues be raised in code review?▼

Raise performance concerns only when the change creates a plausible or measured impact, such as new queries in hot paths or unbounded loops. Speculative performance issues without a concrete failure mode should not be reported.