skills.rest
nirholas
nirholasCOMMUNITY
Explore all skills by this author →
Website𝕏@nichxbtGitHub

code-review

Review Git branch changes between base-branch and HEAD for issues.

71|22|Updated Apr 6, 2020
Search Tags:#git#quality#conventions#diff#code-review#pull-request
One-click install
npx skills add https://github.com/nirholas/agenti --skill code-review-nirholas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/nirholas/agenti/tree/main/packages/protocols/x402-faremeter/skills/code-review
Command: npx skills add https://github.com/nirholas/agenti --skill code-review-nirholas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides reviewers to focus on changes introduced by a branch, ensuring that reviews target new logic and behavior rather than pre-existing code.

Core Features & Use Cases

  • Scope-aware diffs: compare base-branch to HEAD to identify relevant changes.
  • Conformance and quality checks: verify adherence to project conventions, naming, and patterns.
  • Use Case: a reviewer uses this workflow to assess a PR before merging, surfacing potential bugs and consistency issues.

Quick Start

Review the current branch against the base to surface changes and propose concrete improvements.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review only the new code changes in a pull request?▼

To review only new code changes in a pull request, you can compare the base-branch to HEAD using git diff. This surfaces relevant modifications and evaluates bug risks while ignoring pre-existing code.

What is the best way to enforce project conventions during a branch review?▼

The best way to enforce project conventions during a branch review is to use a guided checklist tied to CONVENTIONS.md. This verifies naming, pattern adherence, and style conformance for the specific changes introduced.

How does scope-aware git diff work for PR feedback?▼

Scope-aware git diff works for PR feedback by comparing the base-branch against HEAD to isolate introduced logic. It targets new behavior and delegates detailed analysis to sub-agents to surface potential bugs.

Can I assess multiple commits in a single branch review workflow?▼

Yes, you can assess multiple commits in a single branch review workflow. The process evaluates changes across a set of commits or a single PR to identify bug risks and consistency issues before merging.

Does this code review process work without external dependencies?▼

Yes, this code review process works without external dependencies. It relies solely on Git-based project workflows, applying scope rules to evaluate changes and guide reviewers without requiring additional tool installations.

Why should I focus on diffs between the base-branch and HEAD?▼

Focusing on diffs between the base-branch and HEAD ensures reviews target new logic and behavior rather than pre-existing code. This approach streamlines branch reviews by surfacing only relevant modifications for quality checks.

Related Skills

Explore More Software Engineering Skills→
harnessprotocolharnessprotocol
9

review

Produce structured code reviews for diffs, PRs, or scoped paths.

Official
Intermediate
catu-aicatu-ai
12

harness-land

Merge an approved pull request after confirming an archived harness plan.

Official
Intermediate
tilework-techtilework-tech
149

Finishing a Development Branch

Run tests, formatters, linters, type checks, and submit a PR.

Official
Intermediate
jm199seojm199seo

review

Analyze pull request diffs against the base branch for structural issues.

Community
Advanced