git-workflow-and-versioning

To structure a git workflow for multiple agents, use short-lived feature branches and git worktrees to isolate parallel experiments. This prevents chaotic changes and ensures all commits remain small, traceable, and reviewable before merging into main.

The best way to write atomic git commits is to group focused changes with descriptive messages that explain intent. Following project commit type conventions preserves history and keeps code changes meaningful and reversible during feature development.

Pre-commit checks on feature branches require a staged-diff review, secret scanning, tests, linting, and type checks before committing. This hygiene gate ensures that only verified, clean code changes merge quickly into the main branch.

You need git worktrees when running parallel experiments or agent workflows without branch switching. Worktrees isolate changes in separate directories, allowing concurrent feature development while keeping code changes safe and reviewable.

Yes, this git versioning approach satisfies trunk-based development requirements by guiding short-lived feature branches, atomic commits, and pre-commit verification gates. It ensures changes merge quickly and cleanly into the main trunk.

Running pre-commit checks before merging generated files ensures that linting, type checks, and secret scanning validate all changes. This prevents unreviewable or broken modifications from entering the main branch and maintains commit hygiene.