PR descriptions and commit messages convention for our PRs

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: *<type>: <subject>*

Type:

• feat: new feature for the user, not a new feature for build script
• fix: bug fix for the user, not a fix to a build script
• docs: changes to the documentation
• style: formatting, missing semi-colons, etc; no production code change
• refactor: refactoring production code, eg. renaming a variable
• test: adding missing tests, refactoring tests; no production code change
• chore: updating pre-commit tasks, packages, etc; no production code change

Example

feat: add hat wobble
^--^  ^------------^
|     |
|     +-> Summary in the present tense.
|
+-------> Type: chore, docs, feat, fix, refactor, style, or test.

PR Description

# PR Title

## Context and Problem Statement
[Describe the issue or background that led to this change. What problem are we solving?]

## Solution
[Explain the solution implemented, focusing on the approach and key technical decisions]

Key changes:
- [Bullet points highlighting the main changes]
- [Focus on what changed, not how it changed]
- [Include architectural decisions if relevant]

## Testing
- [ ] [Specific test case 1]
- [ ] [Specific test case 2]
- [ ] [Edge cases tested]
- [ ] [Regression testing performed]

## Impact
[Describe the user-facing impact and any potential side effects or considerations]