code-review

Generate inline GitHub PR comments and a summary verdict for code changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines code reviews by producing inline GitHub PR comments and a concise summary, ensuring consistent, constructive feedback across diffs.

Core Features & Use Cases

  • Inline PR comments anchored to exact lines with a severity-prefixed verdict.
  • Single, cohesive review payload per diff to avoid notification sprawl.
  • Supports multiple modes (PR by default, --pending, --commit, and codebase scans) with configurable flags like --dry-run, --post, and --no-inline.

Quick Start

Invoke the review on a PR or diff to generate inline comments and a final verdict.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate inline code review comments on a GitHub pull request?

Automate inline code review by generating severity-prefixed PR comments anchored to exact diff lines and a concise summary verdict. The skill outputs a single, post-ready review payload to ensure consistent, constructive feedback across changes without notification sprawl.

Can I review pending changes or specific commits instead of a full pull request?

Yes, you can review pending changes or specific commits instead of a full pull request. The skill supports multiple modes including --pending for uncommitted work and --commit for individual commits, alongside its default PR review and full codebase scan functionality.

How does the dry run mode work for automated PR reviews?

The dry run mode for automated PR reviews generates the inline comments and summary verdict without posting them to GitHub. You invoke the review with the --dry-run flag to safely preview the severity-prefixed feedback and post-ready payload before publishing.

What is the best way to avoid notification sprawl when reviewing large diffs?

To avoid notification sprawl when reviewing large diffs, enforce a one-review-per-PR rule that consolidates all feedback into a single, cohesive review payload. This ensures the inline comments and final verdict are posted together rather than as separate notifications.

Does this code review tool support posting comments directly to GitHub?

Yes, this code review tool supports posting comments directly to GitHub. By invoking the review with the --post flag, the skill submits the generated inline PR comments and concise summary verdict directly to the repository.

Can I generate a code review summary without inline comments?

Yes, you can generate a code review summary without inline comments. By applying the --no-inline flag, the skill suppresses the line-anchored feedback and outputs only the concise summary verdict for your diff or codebase scan.