commit-readiness-checker

Pre-commit readiness validation checks your version bump, changelog entry, and file synchronization before committing. This ensures documentation like README and CLAUDE.md matches the new version, preventing incomplete releases.

Checking version bump and CHANGELOG synchronization involves verifying version.json and CLAUDE.md against your release notes. This process ensures files are synced before commit, providing deterministic blockers and actionable guidance to fix any missing entries.

You can auto-generate a git commit message from release notes and versioning changes. After verifying a clean git status and successful readiness checks, an automatic commit message draft is created and aligned with your release notes.

Pre-commit release readiness verification is a validation process ensuring version bumps, changelog entries, and documentation are synchronized before a commit. It applies to software release workflows requiring deterministic blockers to prevent incomplete releases and post-commit fixes.

Yes, the readiness checker works without external dependencies. It performs full readiness checks by reading multiple internal sources like version.json, CLAUDE.md, README, and SETUP_CONTEXT directly, requiring no additional components or external packages to function.

Your pre-commit readiness check fails on git status when the working directory is not clean. The validation requires a clean git status before committing, providing actionable blockers and next steps to guide you in resolving any uncommitted changes or missing version updates.