review

Automate code review of diffs or files with a security-scan pipeline.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/This-HW/hantu_quant --skill review-this-hw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/This-HW/hantu_quant/tree/main/.claude/skills/review
Command: npx skills add https://github.com/This-HW/hantu_quant --skill review-this-hw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the process of reviewing code changes by analyzing diffs or specified files, providing structured feedback and findings.

Core Features & Use Cases

  • Automated review of diffs or target files using a defined pipeline (review-code → security-scan).
  • Supports review across multiple languages and project types, suitable for integration into CI pipelines.
  • Produces concise results with actionable suggestions and risk findings, ready for review and remediation.

Quick Start

Provide a target file path or a diff to start the automated code review.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for git diffs and pull requests?

You can automate code review by providing a diff or target file path to process changes. The pipeline runs a review-code step followed by a security-scan, returning structured findings suitable for CI integration.

Can I run static analysis and security scans on specific file paths?

Yes, static analysis and security scans can be run on explicit file paths. The automated review pipeline applies static analysis to the specified files and outputs concise risk findings.

Does the automated code review work across multiple programming languages?

The automated code review supports multiple languages and project types. It processes provided diffs or files to generate actionable suggestions and structured risk findings.

What is the best way to integrate code review into a CI pipeline?

The best way to integrate code review into CI is using a two-step pipeline that outputs structured findings. This approach analyzes diffs or commits and returns actionable suggestions ready for remediation.

How does the two-step review-code and security-scan pipeline work?

The pipeline works by first executing the review-code step to analyze changes, followed by the security-scan step to identify vulnerabilities. It produces structured findings for quick remediation.