edi-save-commit

To automatically commit changes and log project activity, you can use a workflow that stages non-binary source updates and generates JSONL activity entries under .activity/YYYY-MM.jsonl. This creates auditable records capturing file paths and sizes for every project modification.

An activity log in JSONL format for git commits records project changes as structured entries under .activity/YYYY-MM.jsonl. It captures file paths and sizes, enabling an auditable trail of updates across core editing directories.

Yes, you need write permissions to automate git commits for project management. The process requires Git access to stage and commit changes in 01-source, and the ability to emit JSONL activity entries to maintain the audit trail.

To create an auditable record of file changes in a project directory, commit updates and generate per-project JSONL log entries. These entries capture file paths and sizes, providing a structured activity log for project materials.

You should not use automated git commits for source updates when working with binary files, as the process stages only non-binary source changes. Additionally, it requires project conventions to determine commit boundaries and log policies for consistency.