review-dirty

Review dirty git changes and output structured JSON feedback.

17|3|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/ksleungac/pids-jre-simulator --skill review-dirty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-dirty
Source: https://github.com/ksleungac/pids-jre-simulator/tree/main/.claude/skills/review-dirty
Command: npx skills add https://github.com/ksleungac/pids-jre-simulator --skill review-dirty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews dirty code changes in a repository using Claude Code Agent to surface issues before they are merged.

Core Features & Use Cases

  • Gathers git status and diffs via PowerShell-based workflow to identify problematic changes.
  • Generates structured, actionable feedback suitable for developer reviews and code QA.
  • Non-destructive: does not modify code or commit any changes during review.

Quick Start

Run the review-dirty skill on your repository to generate a structured report detailing issues in dirty changes.

Frequently Asked Questions about review-dirty

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

FAQPage Schema
How do I review uncommitted git changes before merging?▼

To review uncommitted git changes, this skill gathers git status and diffs via PowerShell to identify problematic dirty code and generates structured feedback without modifying files.

Can I automate code review for dirty changes on Windows?▼

Yes, you can automate code review for dirty changes on Windows using PowerShell-based workflows to collect git diffs and output structured, actionable feedback in JSON format.

Does this code review tool modify my repository files?▼

No, this code review tool is non-destructive and does not modify repository files or commit changes, ensuring your dirty changes remain untouched during the QA process.

What is the output format for automated code review feedback?▼

The output format for automated code review feedback is a machine-readable JSON structure, providing actionable insights into dirty code changes gathered from git status and diffs.

Do I need PowerShell to run automated git diff reviews?▼

Yes, you need PowerShell to run automated git diff reviews, as all shell commands for gathering git status and diffs within this Windows-based workflow require it.