review

Reviews local uncommitted git changes with Jira ticket context and routes diffs to specialized review skills.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/hanh-nd/agent-kit --skill review-hanh-nd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/hanh-nd/agent-kit/tree/main/plugins/agent-kit/.gemini/skills/review
Command: npx skills add https://github.com/hanh-nd/agent-kit --skill review-hanh-nd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing uncommitted local changes before pushing is often skipped or inconsistent, and reviewers lack ticket context about why the code changed. This Skill automates the pre-push review by computing a clean diff, pulling Jira intent from the branch name, and delegating to the right review skill. ## Core Features & Use Cases - Noise-filtered diff computation: Excludes lockfiles, build artifacts, minified assets, and snapshots while deliberately keeping .env files and migrations in scope for security review. - Automatic Jira context: Extracts a ticket ID from the current branch name and fetches the ticket body as review intent, without blocking if unavailable. - Intelligent routing: Detects whether changes are production code, E2E tests, or mixed, and delegates to code-review, e2e-review, or both, then assembles a single report with branch, base, and file-count header. - Use Case: Before pushing a feature branch PROJ-123, run the review to get a structured report of your staged and unstaged changes evaluated against the Jira ticket's intent, with a footnote flagging untracked files. ## Quick Start Ask the agent to review my local changes against the main branch using the review skill.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review uncommitted local changes before pushing?▼

Run the review skill with no arguments to diff against HEAD, covering all staged and unstaged changes to tracked files. It computes the diff, detects Jira context from your branch, and returns a structured review report.

How do I review changes against a specific branch or commit?▼

Pass the base branch or commit as an argument, such as main or a commit SHA. The skill runs git diff against that target instead of the default HEAD and reviews everything changed since that point.

Does the review include untracked files in git?▼

No, untracked files are outside git diff and cannot be reviewed. The report appends a footnote with the untracked count and suggests running git add -N . or git add -A, then re-running the review.

Can code review use Jira ticket context automatically?▼

Yes, the skill extracts a ticket ID pattern like PROJ-123 from the current branch name and fetches the ticket body as review intent. If the lookup fails or no ticket exists, the review proceeds without intent.

Why are lockfiles and build artifacts excluded from the diff?▼

Files like package-lock.json, dist output, minified assets, and snapshots add noise without review value, so they are excluded. Notably, .env files and migrations are kept in scope because secret leaks and destructive operations need review.

What happens when a diff contains both production code and E2E tests?▼

The skill detects mixed diffs and splits them by file type, routing production code to code-review and Playwright or Cypress changes to e2e-review. Both verdicts are then combined into a single report.