What: Brief description of the changes
Why: The problem this solves or feature this adds
Linked Issues: Closes #[issue_number] | Fixes #[issue_number] | Related to #[issue_number]

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (code change that neither fixes a bug nor adds a feature)
• Documentation (changes to README, guides, comments)
• Tests (adding missing tests or correcting existing tests)
• Performance improvement

1. Backend Setup (if applicable):

   cd backend
   npm install
   npm run dev

2. Extension Setup (if applicable):

   • Open chrome://extensions
   • Enable Developer Mode
   • Load unpacked extension from /extension folder

3. Test Steps:

   • Step 1: ...
   • Step 2: ...
   • Step 3: ...

• Chrome (Version: ___)
• Windows/Mac/Linux
• Backend API (if applicable)

• I read and followed CONTRIBUTING.md
• I tested my changes thoroughly
• I updated documentation where needed

• Code follows existing style conventions
• Added comments for complex logic
• No commented-out code left behind
• No unnecessary dependencies added

• Changes work as expected
• No existing functionality is broken
• Error handling is appropriate
• Performance impact considered

• Extension loads without errors (if applicable)
• Backend API works correctly (if applicable)
• UI follows existing theme system (if applicable)

Questions for Reviewers:

• Any specific areas you'd like extra attention on?

Breaking Changes: [List any breaking changes and migration steps]

Future Work: [Any follow-up work needed?]