code-review

Analyze git diffs and commits between two references for code quality and security.

Updated Sep 28, 2021

Search Tags:#git #quality #diff #code-review #analyze #commit-messages

Ready to run

npx skills add https://github.com/hhk7734/hhk7734 --skill code-review-hhk7734

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps engineers assess software changes by analyzing diffs, review history, and feedback mechanisms to enforce quality and adherence to project conventions.

Core Features & Use Cases

Compare base_ref and target_ref to surface changes across commits and diffs.
Review commit messages for conventional patterns and semantic clarity.
Provide feedback on maintainability, performance, and security implications.
Support pre-merge inspections by summarizing impact and risks.

Quick Start

Identify two git references (base_ref and target_ref) and generate a structured review highlighting key changes and recommended actions.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I review code changes between two git branches before merging?▼

Reviewing code changes between two git branches requires analyzing diffs and commits between base_ref and target_ref. This generates a structured review focusing on code quality, maintainability, and security implications, summarizing impact and risks for pre-merge inspections.

What is the difference between three-dot and two-dot diff strategies for code review?▼

Three-dot and two-dot diff strategies handle git reference comparisons differently during code review. Three-dot strategy compares changes since the common ancestor, while two-dot strategy compares direct differences between two specific commits to assess code quality and security implications.

Can I analyze commit messages for conventional patterns using a git diff?▼

Yes, analyzing commit messages for conventional patterns and semantic clarity is possible using a git diff. The review evaluates commit history against project conventions to enforce quality and adherence, applying to feature branches, tags, or arbitrary commits.

What is the best way to assess maintainability and security risks in a feature branch?▼

The best way to assess maintainability and security risks in a feature branch is comparing base_ref and target_ref using diff strategies. This surfaces changes across commits, providing feedback on performance and security implications for pre-merge inspection.

Do I need specific dependencies to analyze arbitrary git commits for code quality?▼

No specific dependencies are required to analyze arbitrary git commits for code quality. You need to identify two git references, and the skill handles diff strategies and commit message evaluation against conventions natively.