docs: add format instructions

Author: lpm0073

SEMANTIC_VERSIONING.md

@@ -1,5 +1,21 @@
 # Semantic Versioning Guide
 
+See [Conventional Commits](https://www.conventionalcommits.org/)
+
+As an open-source maintainer, squash feature branches onto master and write a standardized commit message while doing so. The commit message should be structured as follows:
+
+```code
+<type>: This represents the type of change made in the commit. Common types include feat (for a new feature), fix (for a bug fix), chore (for routine tasks like updating dependencies), docs (for documentation changes), style (for code style changes), refactor (for refactoring existing code), test (for adding or updating tests), and perf (for performance improvements).
+
+[optional scope]: This is an optional part that provides additional contextual information, like the part of the codebase the commit modifies.
+
+<description>: This is a brief description of the changes the commit makes.
+
+[optional body]: This is an optional part where you can provide a more detailed explanation of the changes.
+
+[optional footer(s)]: This is also optional and is often used to reference issue tracker IDs.
+```
+
 ## Commit Message format
 
 - `feat`: A new feature