code-review

Automate structured code quality reviews on pull requests across languages and repositories.

23|2|Updated May 27, 2026

Search Tags:#security #review #risk-assessment #static-analysis #code-review #pull-request

Ready to run

npx skills add https://github.com/zhouguoqing/QianYuan.AIAgenticFramework --skill code-review-zhouguoqing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/zhouguoqing/QianYuan.AIAgenticFramework/tree/main/samples/skills/code-review
Command: npx skills add https://github.com/zhouguoqing/QianYuan.AIAgenticFramework --skill code-review-zhouguoqing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates structured code quality reviews by surfacing bugs, regressions, and security risks.

Core Features & Use Cases

Automated Findings: Generate prioritized findings with rationale tied to specific files and code symbols.
Risk & Coverage: Highlight data-loss or security risks, missing tests, and test gaps.
Use Case: For a PR with multiple changes, produce a concise report listing critical issues first and suggested fixes.

Quick Start

Run a review on the target pull request to instantly surface critical issues and recommended fixes.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I automate code review for a pull request?▼

Automated code review runs directly on pull requests to surface bugs, regressions, and security risks. It analyzes diffs to generate prioritized findings with concrete file references and actionable fixes.

What is static analysis for risk assessment in code changes?▼

Static analysis for risk assessment evaluates code artifacts to identify data-loss and security risks before merging. It prioritizes findings by severity and provides rationale tied to specific files and symbols.

Can I use automated code review across multiple programming languages?▼

Yes, automated code review applies across languages and repositories. It analyzes code artifacts and diffs in pull requests to perform pre-merge checks and code-change audits regardless of language.

How do I find missing tests and coverage gaps in a pull request?▼

Code review identifies missing tests and test gaps by analyzing pull request diffs. It highlights these coverage risks alongside critical issues to ensure comprehensive pre-merge validation.

What is the best way to prioritize security findings in a pre-merge check?▼

Pre-merge checks generate a concise report listing critical security findings first. This prioritized output includes rationale and suggested fixes directly tied to the changed code symbols.

Why does my code review report list critical issues separately from minor fixes?▼

Code review reports list critical issues first to surface high-impact bugs, regressions, and security risks immediately. This prioritization ensures developers address dangerous data-loss risks before minor suggestions.