code-reviewer

Review local diffs or GitHub pull requests and produce structured findings.

Updated Aug 30, 2025
One-click install
npx skills add https://github.com/vonomarap/kanokna --skill code-reviewer-vonomarap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/vonomarap/kanokna/tree/main/.agents/skills/code-reviewer
Command: npx skills add https://github.com/vonomarap/kanokna --skill code-reviewer-vonomarap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and reviewers produce consistent, actionable, and thorough code reviews for both local changes and remote pull requests, reducing regressions and improving long-term code quality.

Core Features & Use Cases

  • Remote PR Reviews: Checkout GitHub pull requests, read PR descriptions and comments, and run preflight checks before analysis.
  • Local Change Reviews: Inspect staged and unstaged diffs to evaluate correctness, readability, error handling, and test coverage.
  • Structured Feedback: Produce a clear summary with critical issues, suggested improvements, nitpicks, and a final recommendation (Approve or Request Changes).

Quick Start

Ask the agent to review PR #123 or to review my local changes to analyze diffs and produce a structured review.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I conduct a code review for a GitHub pull request using an AI agent?

To conduct a code review for a GitHub pull request, the agent checks out the PR, reads the description and existing comments, and optionally runs preflight verification commands before producing a structured summary with prioritized findings and a final recommendation.

Can I review local staged and unstaged diffs for correctness and maintainability?

Yes, you can review local staged and unstaged diffs to evaluate correctness, maintainability, readability, efficiency, security, and testability, receiving concrete fixes and a clear approval or request changes recommendation.

What is the best way to analyze a diff and ensure test coverage before merging?

The best way to analyze a diff and ensure test coverage is to run preflight verification commands and inspect the changes for testability, allowing the agent to suggest concrete tests and highlight critical issues before merging.

Does the code review process check for security and efficiency issues in local changes?

Yes, the code review process specifically checks local changes for security vulnerabilities and efficiency problems, applying a structured analysis to identify critical issues, suggest improvements, and output a prioritized recommendation.

How do I get structured feedback with concrete fixes for my pull request?

You get structured feedback with concrete fixes by asking the agent to review your pull request or local changes, which evaluates the diff against multiple quality criteria and outputs a clear summary of critical issues, improvements, and nitpicks.

When should I use an automated code reviewer instead of manual inspection?

You should use an automated code reviewer when you need consistent, actionable, and thorough analysis of local changes or remote pull requests to reduce regressions and improve long-term code quality across multiple developers.