review-changes

Review uncommitted code changes for bugs, security vulnerabilities, and style violations.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/AndersonsRepo/AI-Harness --skill review-changes-andersonsrepo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-changes
Source: https://github.com/AndersonsRepo/AI-Harness/tree/main/.claude/skills/review-changes
Command: npx skills add https://github.com/AndersonsRepo/AI-Harness --skill review-changes-andersonsrepo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of reviewing code changes, identifying potential bugs, security vulnerabilities, and style inconsistencies before they are committed.

Core Features & Use Cases

  • Automated Code Analysis: Scans staged, unstaged, or all code changes against a comprehensive checklist.
  • Bug Detection: Identifies logic errors, incorrect error handling, and race conditions.
  • Security Auditing: Checks for command injection, path traversal, and exposed secrets.
  • Style Enforcement: Ensures adherence to coding conventions and project-specific guidelines.
  • Use Case: Before pushing a feature branch, run this skill to catch a potential SQL injection vulnerability in a new database query and ensure consistent naming conventions across all modified files.

Quick Start

Use the review-changes skill to review all unstaged code changes.

Frequently Asked Questions about review-changes

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

FAQPage Schema
How do I review uncommitted code changes for bugs and security vulnerabilities?

Review uncommitted code changes by scanning staged, unstaged, or all file modifications against a comprehensive checklist to identify logic errors, command injection, path traversal, and exposed secrets.

Can I check only staged files for security vulnerabilities and style violations?

Yes, you can check only staged files for security vulnerabilities and style violations by specifying staged file modifications as an argument when initiating the code review.

What types of security vulnerabilities can automated code analysis detect before pushing a feature branch?

Automated code analysis can detect security vulnerabilities including command injection, path traversal, and exposed secrets, alongside logic errors, incorrect error handling, and race conditions.

Does the code review process enforce coding conventions and project-specific guidelines?

Yes, the code review process enforces adherence to coding conventions and project-specific guidelines, including specific guardrails for Claude CLI usage, to ensure consistent style across modified files.

Is there a way to catch race conditions and incorrect error handling in unstaged code modifications?

Catch race conditions and incorrect error handling in unstaged code modifications by running an automated code analysis that targets all unstaged file modifications for comprehensive bug detection.

What is the best way to automate bug detection in git changes before committing?

Automate bug detection in git changes by analyzing uncommitted modifications against a predefined checklist to identify logic errors, security flaws, and style inconsistencies before they are committed.