change-log-guard

To automate structured change logs for code and configuration modifications, this Skill enforces a standardized log format and automatically writes entries to your repository's CHANGE-LOG.md whenever files are added, modified, or deleted.

The best way to ensure traceability and compliance for git repository changes is to enforce structured logging of every modification, capturing the change type, rationale, verification steps, and next actions directly in CHANGE-LOG.md.

You record change rationale and verification steps in a CHANGE-LOG.md file by applying a standardized log template that documents the change type, rationale, verification steps, and next actions for each real modification.

Yes, this change log automation works for documentation and rule changes as well as code, applying uniformly to any new additions, modifications, or deletions across projects to maintain consistent compliance.

When a development round has no actual modifications, the process requires explicitly stating that no changes occurred, ensuring the log remains accurate and preventing empty or misleading entries.

You should enforce a standardized format for change logs instead of free text entries to guarantee structured traceability, ensuring that every modification consistently documents its type, rationale, verification steps, and next actions for compliance.