CJ_document-release

Automating document release in a git repository involves validating files against a contract and committing changes. This skill reads the doc-spec.md contract, audits specified documents, halts on errors, and auto-commits document-only changes after a successful release.

Doc-spec.md contract enforcement works by reading the contract file to validate documents during release. If the contract is missing, the process self-heals by bootstrapping from a portable seed, ensuring compliance and consistency across the project before committing.

Yes, you can release a specific subset of documents by providing a comma-separated list of document names. The release process filters the documents based on this list, auditing and committing only the specified files if they pass the contract checks.

If errors are detected during a document release audit, the process immediately halts. This halt-on-red mechanism prevents non-compliant documents from being committed, ensuring that only validated and consistent document changes are included in the repository.

Yes, you need Bash, Read, Glob, and Grep tools to enforce document compliance. The release process relies on these tools to read the doc-spec.md contract, search and filter files, and execute git commands to automatically commit document-only changes.