jack-git-commit

Atomic git commits with conventional commit formatting are generated by staging specific changes and creating a message structured as type(scope): subject, ensuring each commit represents a single logical change with an appropriate type like feat, fix, or refactor.

Adding provenance metadata to git commit messages involves appending structured footers such as Goal, Step, and Worker to the commit body, creating a self-documenting history and a traceable ledger of work performed on the codebase.

The allowed types for conventional commits in this structured workflow are feat, fix, refactor, docs, test, chore, style, and perf, ensuring commit discipline and categorizing changes accurately across the version control history.

No, this git commit workflow does not automatically push changes to the remote repository. It enforces commit discipline by focusing on staged-only workflows and creating atomic commits, requiring manual intervention for pushing.

The scope for a conventional commit message is determined specifically by considering the primary module affected by the changes, ensuring the commit accurately reflects the area of the codebase being modified.

Including a body in a conventional commit message explains why the change was made, providing essential context beyond the subject line and supporting the goal of a self-documenting version control history.