commit-ready

Assess working tree commit readiness by validating tests, docs, specs, and artifacts.

Updated Mar 26, 2026

Search Tags:#git #commit #diff #pre-commit #docs #tests

Ready to run

npx skills add https://github.com/ephes/agent-stuff --skill commit-ready

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit-ready
Source: https://github.com/ephes/agent-stuff/tree/main/pi/skills/commit-ready
Command: npx skills add https://github.com/ephes/agent-stuff --skill commit-ready

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps determine if the current changes are ready to commit, preventing accidental commits and ensuring alignment of tests, docs, specs, and generated artifacts.

Core Features & Use Cases

Inspect the working tree to identify touched files, diffs, and staged vs unstaged changes.
Validate that tests pass, docs are updated, and generated artifacts are in sync before a commit.
Provide a clear readiness verdict and actionable blockers without modifying the repository history.
Offer optional recommendations or fixes for easily resolvable gaps if requested.

Quick Start

Ask me to assess your current changes for commit readiness.

Frequently Asked Questions about commit-ready

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

FAQPage Schema

How do I check if my git changes are ready to commit without actually committing?▼

To check commit readiness without committing, inspect the working tree to identify touched files, diffs, and staged vs unstaged changes. This validates that tests pass, docs are updated, and generated artifacts are in sync before a commit.

What should I validate before making a git commit?▼

Before making a git commit, validate that tests pass, docs are updated, and generated artifacts are in sync. Inspecting the working tree ensures touched files and diffs are reviewed, preventing accidental commits of incomplete changes.

Can I verify staged and unstaged git changes before finalizing a commit?▼

You can verify staged and unstaged git changes by inspecting the working tree. This process reviews diffs and touched files to provide a clear readiness verdict and actionable blockers without modifying repository history.

How do I ensure my tests and docs are updated before committing?▼

To ensure tests and docs are updated before committing, perform repo-native validation steps. This assesses commit readiness by checking the working tree to report blockers and return a clear readiness verdict.

What are the limitations of pre-commit validation for git changes?▼

A limitation of pre-commit validation is that it assesses readiness without creating a commit. While it reports blockers and validates tests, docs, and artifacts, it does not modify repository history or automatically resolve gaps.

Does commit readiness validation modify my git repository history?▼

Commit readiness validation does not modify your git repository history. It inspects the working tree to provide a clear readiness verdict and actionable blockers without creating a commit or altering existing history.