skills.rest
JaimeJunr
JaimeJunrCOMMUNITY
Explore all skills by this author →
GitHub

review

Analyze git diffs and rank issues by severity.

2|Updated Apr 11, 2026
Search Tags:#testing#security#review#code-quality#git-diff
One-click install
npx skills add https://github.com/JaimeJunr/context-mode --skill review-jaimejunr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/JaimeJunr/context-mode/tree/main/.claude/skills/review
Command: npx skills add https://github.com/JaimeJunr/context-mode --skill review-jaimejunr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review de código focado no git diff. Analisa mudanças por correção, segurança, performance e testes. Classifica issues como blocker/warning/suggestion.

Core Features & Use Cases

  • Foco nas linhas alteradas para entender o impacto sem precisar reprocessar o arquivo inteiro.
  • Classifica issues por severidade (Blocker, Warning, Suggestion) para priorização de correções.
  • Suporta validação rápida com linter/testes nos arquivos modificados (quando disponíveis).

Quick Start

Summarize the latest git diff and generate a prioritized review plan.

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 on a git diff to find security and performance issues?▼

Automated code review analyzes git diffs to identify issues across altered lines, focusing on correction, security, performance, and tests. It evaluates changes by applying to pull requests and patch ranges across branches or baselines.

Can I run a focused code review on specific commit ranges like BASE_SHA..HEAD_SHA?▼

Yes, focused code review supports specific commit ranges like BASE_SHA..HEAD_SHA. This ensures the analysis stays strictly within scope, evaluating only the patch range between branches or baselines to isolate issues in altered lines.

What is the best way to prioritize code review issues found in a pull request?▼

The best way to prioritize code review issues is by classifying them according to severity. The review process ranks issues as blockers, warnings, or suggestions, producing structured output to help developers prioritize fixes.

Does this code review process require running linters and tests on modified files?▼

Running linters and tests on modified files is supported for quick validation when available, but it is not strictly required. The core review mechanism focuses directly on analyzing the git diff of altered lines to find issues.

How does analyzing only altered lines improve the code review process?▼

Analyzing only altered lines improves the code review process by understanding the impact of changes without reprocessing the entire file. This targeted git diff analysis isolates scope, ensuring review feedback stays relevant to the patch.

What are the limitations of using git diff analysis for pull request reviews?▼

A limitation of git diff analysis is that it strictly focuses on altered lines, meaning pre-existing issues in unmodified code sections are ignored. The review scope is constrained to the provided patch ranges and branch baselines.

Related Skills

Explore More Software Engineering Skills→
theslashdojotheslashdojo

git-diff

Identify and review exact changes across git states with unified diff output.

Official
Advanced
hamsuranghamsurang
19

skill-review

Audit SKILL.md files against best practices and produce structured pass/fail reports.

Official
Intermediate
OneWave-AIOneWave-AI
245

code-review-pro

Review code for security vulnerabilities, performance bottlenecks, and maintainability issues.

Official
Basic
DevHive1DevHive1
18

security_scan

Orchestrate dependency, static analysis, and privacy dataflow scanners into prioritized reports.

Community
Advanced