# Pull Request

## Description

<!-- Provide a clear and concise description of what this PR does -->

## Type of Change

<!-- Mark the relevant option(s) with an "x" -->

- [ ] 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)
- [ ] Documentation update
- [ ] Performance improvement
- [ ] Code refactoring
- [ ] Test improvements
- [ ] CI/CD improvements

## Motivation

<!-- Why is this change needed? What problem does it solve? -->
<!-- Link to any related issues: Fixes #123, Closes #456, Related to #789 -->

## Changes Made

<!-- List the main changes made in this PR -->

- 
- 
- 

## Testing

<!-- Describe how this change has been tested -->

### Test Environment
- OS: <!-- e.g. Windows 11, macOS 14.0, Ubuntu 22.04 -->
- Python version: <!-- e.g. 3.9.18 -->
- Testing approach: <!-- Unit tests, manual testing, integration tests, etc. -->

### Test Results
<!-- Describe test results, include relevant output if helpful -->

```bash
# Example test commands and output
make test
# ... test output ...
```

## Screenshots/Examples

<!-- If applicable, add screenshots or example output to help explain your changes -->

## Checklist

<!-- Mark completed items with an "x" -->

### Code Quality
- [ ] My code follows the project's style guidelines
- [ ] I have performed a self-review of my code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings

### Testing
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] New and existing unit tests pass locally with my changes
- [ ] I have checked that my changes don't break existing functionality

### Documentation
- [ ] I have updated the documentation (if applicable)
- [ ] I have updated the CHANGELOG.md (if applicable)
- [ ] I have added/updated type hints where appropriate

### Git & Process
- [ ] I have used descriptive commit messages
- [ ] I have followed the conventional commits format (feat:, fix:, docs:, etc.)
- [ ] I have rebased my branch against the latest main branch
- [ ] I have resolved any merge conflicts

## Breaking Changes

<!-- If this PR introduces breaking changes, describe them here -->
<!-- Include migration instructions if applicable -->

## Additional Notes

<!-- Any additional information that reviewers should know -->

## Review Guidelines

<!-- For reviewers -->
**For Reviewers:**
- [ ] Code follows project conventions and style
- [ ] Changes are well-tested and documented
- [ ] PR title and description are clear and informative
- [ ] No unnecessary changes or files included
- [ ] Performance impact considered (if applicable)

---

<!-- 
Thanks for contributing to Azure Functions Doctor! 

Please ensure you have read our CONTRIBUTING.md guide before submitting this PR.
If this is your first contribution, welcome to the community!
-->