ai-code-review-ai-kit

Review added or modified PR diff lines for bugs, security, and reliability risks.

Updated May 11, 2026
One-click install
npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill ai-code-review-ai-kit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ai-code-review-ai-kit
Source: https://github.com/ducthang-hub/nw-ai-kit/tree/main/.agents/skills/ai-code-review-ai-kit
Command: npx skills add https://github.com/ducthang-hub/nw-ai-kit --skill ai-code-review-ai-kit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps teams quickly review changed code by focusing on production-impacting risks (bugs, security, reliability) and turning them into concise, easy-to-action feedback.

Core Features & Use Cases

  • Risk-first diff review: Reviews ONLY added or modified code and prioritizes issues by severity and production impact.
  • Structured findings output: Produces a consistent review report with clear categories like requiring attention, potential improvements, and suggestions.
  • Line-precise citations: References file and line ranges using the required markdown link format for fast navigation.

Quick Start

Use the ai-code-review-ai-kit skill when you are ready to review a PR diff and ask for a risk-first review of the changed lines.

Frequently Asked Questions about ai-code-review-ai-kit

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

FAQPage Schema
How do I perform a risk-first code review on a pull request diff?

Risk-first code review evaluates added or modified lines in a PR diff to prioritize bugs, security issues, and reliability regressions. It produces a structured markdown report with severity-based findings and line-precise citations for fast navigation.

What is the best way to focus code review on security risks and reliability regressions?

Focusing code review on security risks involves analyzing only changed code lines to catch production-impacting vulnerabilities. This approach categorizes findings into requiring attention, potential improvements, and suggestions to ensure critical risks are addressed first.

How do I generate structured markdown feedback with line-based citations for changed code?

Generating structured markdown feedback requires scanning added or modified diff lines and outputting categorized findings. The review includes file and line range markdown links, enabling developers to navigate directly to requiring-attention issues.

Can I use automated diff analysis to assess software quality for modified lines only?

Automated diff analysis assesses software quality by reviewing exclusively added or modified lines in a pull request. It mandates running a code-debt tech scan on the change set to identify reliability and security risks efficiently.

Does code review for pull requests work without reviewing the entire codebase?

Code review for pull requests works by targeting only the added or modified lines in the diff, not the entire codebase. This focused approach reduces review time while still identifying bugs, security issues, and reliability regressions.

When should I not use a risk-first diff review for quality feedback?

Risk-first diff review should not be used when you need to assess overall architecture or untouched legacy code, as it exclusively targets added or modified lines in a PR diff for security and reliability risk assessment.