CONTRIBUTION.md

# Contributing to Insurance Advisor Agent(s)

We are excited that you are interested in contributing to the Insurance Advisor Agent(s) project! Your contributions are invaluable to us. Please follow the guidelines below to contribute.

## How to Contribute

### Reporting Issues
If you find any bugs or have any suggestions for improvements, please report them by opening an issue in the repository.

### Fork and Pull Request Workflow
1. **Fork the Repository**: Click the "Fork" button on the top right of the repository page.
2. **Clone Your Fork**:
   ```sh
   git clone https://github.com/your-username/insurance-advisor-agent.git
   cd insurance-advisor-agent

3. **Create a Branch**:
   ```sh
   git checkout -b feature-branch

4. **Make Your Changes: Make the necessary changes in your branch.**
5. **Commit Your Changes**:
   ```sh
   git add .
   git commit -m "Description of the changes"

6. **Push to Your Fork**:
   ```sh
   git push origin feature-branch

7. **Create a Pull Request: Go to the original repository on GitHub and click "New Pull Request". Select your branch and submit your pull request.**

# Pull Request Template

## Description
Please include a brief description of the changes introduced by this PR.

## Related Issue(s)
- If this PR addresses a particular issue, please reference it here using GitHub's linking syntax, e.g., "Fixes #123".
- If there's no related issue, briefly explain the motivation behind these changes.

## Changes Made
Please provide a list of the changes made in this PR.

## Screenshots (if applicable)
If the changes include UI updates or visual changes, please attach relevant screenshots here.

## Checklist
- [ ] I have tested my changes locally and ensured that they work as expected.
- [ ] I have updated the documentation (if applicable).
- [ ] My code follows the project's coding conventions and style guidelines.
- [ ] I have added appropriate test cases (if applicable).
- [ ] I have reviewed my own code to ensure its quality.

## Additional Notes
Add any additional notes or context about this PR here.

## Reviewer(s)
- @reviewer1
- @reviewer2