review-and-commit

Review code changes for quality, QA, and documentation compliance before committing.

Updated May 16, 2026

Search Tags:#quality assurance #code review #software development #repository management #commit workflow

Ready to run

npx skills add https://github.com/korchasa/flowai-plugins --skill review-and-commit-korchasa

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-and-commit
Source: https://github.com/korchasa/flowai-plugins/tree/main/plugins/flowai/skills/review-and-commit
Command: npx skills add https://github.com/korchasa/flowai-plugins --skill review-and-commit-korchasa

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill simplifies the process of reviewing and committing code changes in a streamlined two-phase workflow, ensuring high-quality code is committed to the repository.

Core Features & Use Cases

Review Phase: Conducts a thorough review of code changes, checking for QA, code quality, and documentation compliance.
Commit Phase: Manages the synchronization of documentation and commit grouping, ensuring code changes are properly documented and grouped.
Use Case: For a developer working on a feature, this Skill can automatically perform a code review, then commit the changes only if they meet all criteria.

Quick Start

Use the 'review-and-commit' skill to review and commit your code changes.

Frequently Asked Questions about review-and-commit

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

FAQPage Schema

How do I automate code review and commit workflows for my repository?▼

A two-phase commit workflow checks code changes for quality assurance and documentation compliance before committing. This ensures only verified code is committed to the repository.

Can I enforce documentation compliance before committing code changes?▼

Yes, you can enforce documentation compliance before committing code changes by applying a structured commit workflow. This process synchronizes documentation and groups commits to ensure all changes are properly documented.

What is a two-phase commit workflow in software development?▼

A two-phase commit workflow in software development separates code evaluation from repository synchronization. It first conducts a thorough review of code changes, then manages commit grouping and documentation synchronization for compliant code.

Does the code review process check for quality assurance and documentation?▼

Yes, the code review process checks for quality assurance and documentation compliance. It conducts a thorough review of code changes to verify that they meet all criteria before proceeding to the commit phase.

What is the best way to structure commits for a feature in repository management?▼

The best way to structure commits in repository management is using a workflow that groups code changes and synchronizes documentation. This ensures feature commits are properly documented and meet quality standards.

When should I use an automated commit workflow instead of committing directly?▼

You should use an automated commit workflow instead of committing directly when your software development process requires structured code review, quality assurance, and documentation compliance before changes enter the repository.