Verified:GitHub

review-code

Review current branch diffs and classify issues by severity.

1|Updated Aug 25, 2024

Search Tags:#diff analysis #quality assurance #code review #bug detection #git diff #review automation #principal software engineer

Ready to run

npx skills add https://github.com/7loro/dotfiles --skill review-code-7loro

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

현재 브랜치의 변경사항을 Principal Software Engineer 관점에서 심층 리뷰한다. 버그, 보안 취약점, 성능 병목, 가독성 이슈를 식별하고 구체적 개선안을 제시한다.

Core Features & Use Cases

심층 코드 리뷰: 변경된 로직의 의도와 영향 범위를 명확하게 평가한다.
Diff 중심 분석: diff 및 관련 파일(임포트/구조적 인접 파일)을 확인해 주요 변경점을 파악한다.
리뷰 원칙 준수: 변경 의도 요약, 관련 파일 읽기, 이슈 분류를 통해 품질을 높인다.

Quick Start

현재 브랜치의 변경사항을 확인한다. 예: git diff HEAD
변경사항이 있으면 해당 변경사항만 리뷰한다. 다른 커밋은 리뷰하지 않음
변경 의도를 1–2문장으로 요약하고, diff에 포함된 파일 및 관련 파일을 읽어 이슈를 분류한다
필요 시 이슈를 BUG/ISSUE/개선 기회로 분류하고 구체적 개선안을 제시한다

Frequently Asked Questions about review-code

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

FAQPage Schema

How do I automate code review for my current git diff?▼

Code review for your git diff is automated by analyzing active branch changes against a base branch. The Skill reads modified files and adjacent modules to summarize intent and classify issues by severity, providing specific improvement suggestions.

What is the best way to perform diff analysis for bug detection?▼

The best way to perform diff analysis for bug detection is using a Principal Software Engineer perspective. This approach evaluates changed logic intent and impact scope to identify bugs, security vulnerabilities, and performance bottlenecks within the git diff.

Can I review specific commits or do I need to review the entire branch?▼

You review only the current changes on your active branch, not unrelated commits. The Skill targets the specific diff output, such as from git diff HEAD, ensuring the code review remains focused on your latest modifications.

How are identified issues classified during a code review?▼

Identified issues are classified into categories such as BUG, ISSUE, and improvement opportunities. The Skill categorizes code quality problems by defined severity levels and provides specific improvement suggestions based on the analyzed diff.

Does this code review approach check files outside the direct diff?▼

Yes, this code review approach reads related files outside the direct diff. It inspects imported files and structurally adjacent modules to understand the full context and evaluate the true impact scope of the modified logic before classifying issues.