- [ ] **List your preferred Git interfaces.**
→ *Each team member notes their main tool (CLI, IDE integration, GUI client like GitKraken, SourceTree, GitHub Desktop, etc.) in `README` → “VCS Tooling.”*
- [ ] **Question:** How can teammates assist each other across tools?
→ *Agree on common terminology and workflows (e.g. “fetch + rebase” vs “pull”), so commands map cleanly between CLI and GUI. Add a short “Cross-tool cheat sheet” in `/docs/`.*
- [ ] **Use consistent identity settings.**
→ *Ensure `user.name` and `user.email` are correctly configured and match your team contact format. Record the rule in `README`.*
- [ ] **Share useful Git configurations.**
→ *Collect helpful settings (aliases, color.ui, diff tools) in a shared `.gitconfig.example` and commit it to `/docs/`.*
- [ ] **Question:** How will you clone and set up the repo on a new machine?
→ *Document minimal steps in `README` under “Setup from Scratch,” including authentication method (HTTPS, SSH) and any required tooling.*
- [ ] **Provide standard helper scripts or aliases.**
→ *Add lightweight shell or batch scripts (e.g. `git-setup.sh`, `sync-dev.sh`) to simplify repetitive VCS tasks and explain their use in `/scripts/README.md`.*
- [ ] **Ensure IDE Git integrations are aligned.**
→ *Verify that merge, diff, and blame tools show the same line endings and encodings across IDEs. Note any adjustments in `/docs/tooling.md`.*
- [ ] **Enable visible diff & merge tools.**
→ *Configure visual diff/merge tools (e.g. `meld`, `kdiff3`, VS Code diff) for easier peer assistance and reviews. Add config hints to `/docs/tooling.md`.*
- [ ] **Question:** How will you log and share VCS issues or discoveries?
→ *Create an issue label like `vcs-tooling` to collect tips, troubleshooting notes, and improvements to the shared setup.*