ha-code-review

Review uncommitted, staged, commit, branch, or PR changes for concrete regressions.

1.6k|149|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/shiwenwen/hope-agent --skill ha-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ha-code-review
Source: https://github.com/shiwenwen/hope-agent/tree/main/skills/ha-code-review
Command: npx skills add https://github.com/shiwenwen/hope-agent --skill ha-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews often drown in speculative style nitpicks or miss real regressions. This Skill performs a maintainer-grade review of your changes, independently verifying each candidate issue so you only see actionable findings ordered by severity.

Core Features & Use Cases

  • Flexible Review Targets: Inspect staged, unstaged, and untracked changes, a commit or commit range, a branch or PR diff, or a named file or subsystem.
  • Two-Phase Reasoning: Discover candidate issues across correctness, security, concurrency, performance, and cross-module contracts, then verify each one against a concrete triggering scenario before reporting.
  • Strict Finding Bar: Report only discrete, actionable issues with scenario, impact, and fix direction, skipping stylistic preferences and pre-existing problems.
  • Use Case: Before merging a pull request, ask for a review of the PR diff and receive severity-ordered findings with file and line references, or a clear statement that no actionable issues exist.

Quick Start

Ask the agent to review all your uncommitted changes and report only real, actionable findings ordered by severity.

Frequently Asked Questions about ha-code-review

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

FAQPage Schema
How do I review uncommitted changes before committing?

Ask the agent to review all uncommitted changes, and it will inspect staged, unstaged, and untracked files. It reads surrounding code, tests, and callers, then reports only verified actionable findings ordered by severity.

How to review a pull request diff for regressions?

Point the review at the PR or branch diff against the correct base. The skill discovers candidate issues across correctness, security, concurrency, and performance, then verifies each against a concrete triggering scenario before reporting.

What programming languages does this code review support?

The skill targets Rust, TypeScript, TSX, JavaScript, JSX, Python, Go, Java, Kotlin, Swift, C, C++, header files, Ruby, PHP, and shell scripts, as declared in its path filters.

Does the code review modify my code automatically?

No. The default action is inspect and report only. It repairs findings only when you explicitly ask for fixes, and it never edits code in review-only mode.

Why does the review report no findings on my diff?

The skill prefers no finding over a speculative one. If every candidate issue is already guarded by surrounding code or tests, or fails verification, it states directly that there are no actionable findings and notes any real residual verification gaps.