review-changes

Review staged diffs for bugs, style issues, and missing tests.

Updated Jul 24, 2024

Search Tags:#git #testing #pre-commit #quality-assurance #lint #code-review #staged-changes

Ready to run

npx skills add https://github.com/jasonwilmot/little-riddle --skill review-changes-jasonwilmot

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-changes
Source: https://github.com/jasonwilmot/little-riddle/tree/main/.claude/skills/review-changes
Command: npx skills add https://github.com/jasonwilmot/little-riddle --skill review-changes-jasonwilmot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-commit review of staged/modified changes for bugs, style issues, and missing tests.

Core Features & Use Cases

Identify correctness issues, style deviations, and missing tests in changed files.
Ensure consistency with existing code patterns and naming conventions.
Use case: A team can automatically review a PR's changes before merging to enforce quality gates.

Quick Start

Enable pre-commit hooks in your repository and run the hook to review staged changes before committing.

Frequently Asked Questions about review-changes

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

FAQPage Schema

How do I review staged changes for bugs and style issues before committing?▼

To review staged changes for bugs and style issues, you can run a pre-commit hook to analyze your diffs for correctness, consistency, and missing tests before hitting main.

What is a pre-commit code review and how does it enforce quality assurance?▼

A pre-commit code review automatically analyzes staged file changes to identify correctness issues, style deviations, and missing tests. It enforces quality assurance by ensuring consistency with existing patterns before changes are committed.

Can I use automated lint checks to ensure missing tests are caught in git commits?▼

Yes, automated pre-commit checks analyze your git staged changes to catch missing tests and lint violations. This ensures contributors submit commits that meet established testing and quality assurance standards.

Does the pre-commit review work across different languages and repositories?▼

Yes, the pre-commit review applies to software development workflows across languages and repos. It analyzes staged diffs for correctness and test coverage, making it suitable for teams enforcing code quality gates.

What is the best way to enforce code quality gates for pull requests?▼

The best way to enforce code quality gates is enabling pre-commit hooks to automatically review a PR's staged changes. This identifies bugs, style deviations, and missing tests before merging to main.

Do I need a configured pre-commit workflow to review staged changes?▼

Yes, you need a configured pre-commit workflow enabled in your repository. The review requires this setup to analyze your staged changes and identify bugs, style issues, and missing tests effectively.