Style guide to write git history

This guide provides a structured approach to writing maintainable Git history. It categorizes commit messages with prefixes like 'feat', 'chore', 'refactor', 'deploy', and 'docs' to clearly indicate the type of change. For large features, it recommends dividing branches into smaller modules using numerical suffixes. Key general practices include creating PRs, consistent naming, using present tense in commit messages, and utilizing squash merges when appropriate.