speckit-commit

Multi-repository commits are prepared by separating code, tests, and generated docs into a controlled scope, enforcing preflight artifact validation and post-commit message verification before altering local git history.

Commit message formatting for Spec Kit repositories is enforced by applying CoreRuntime commit-message rules, which validate compliance during generation and verify the message structure post-commit before finalizing local changes.

Validation before a multi-repository commit works by requiring artifact checks, acceptance evidence, and test-plan review to ensure only release-ready changes are staged, preventing unrelated user work from being included.

Yes, you can separate code, tests, generated spec docs, and local runtime artifacts when staging a final commit, ensuring controlled scope management commits only the intended files without staging unrelated work.

Yes, preflight artifact validation is required to commit Spec Kit work locally, ensuring acceptance evidence and test-plan reviews pass before generating a compliant commit message and changing local git history.

A validation-first commit flow should be used instead of a standard git commit to eliminate the risk of releasing unfinished work, enforcing scope control, message formatting compliance, and post-commit verification before local git history is changed.