# Pull Request
## Summary
<!-- Provide a brief summary of your changes -->
## Type of Change
<!-- Check the type of change this PR introduces -->
- [ ] 🐛 Bug fix (non-breaking change that fixes an issue)
- [ ] ✨ New feature (non-breaking change that adds functionality)
- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] 📚 Documentation update
- [ ] 🔧 Code refactoring (no functional changes, no api changes)
- [ ] ⚡ Performance improvement
- [ ] 🧪 Test improvement
- [ ] 🏗️ Build/CI changes
- [ ] 🔒 Security improvement
## Related Issues
<!-- Link to related issues -->
Fixes #<!-- issue number -->
Closes #<!-- issue number -->
Related to #<!-- issue number -->
## Changes Made
<!-- Describe the changes in detail -->
-
-
-
## Testing
<!-- Describe how you tested your changes -->
### Test Types Completed
- [ ] Unit tests added/updated
- [ ] Integration tests added/updated
- [ ] Manual testing performed
- [ ] Existing tests still pass
### Test Environment
- [ ] Local development environment
- [ ] Docker container environment
- [ ] Real Gremlin server integration
- [ ] Multiple Node.js versions
### Test Cases
<!-- Describe specific test cases -->
1. **Test Case 1**:
- Setup:
- Action:
- Expected Result:
- Actual Result:
2. **Test Case 2**:
- Setup:
- Action:
- Expected Result:
- Actual Result:
## Security Considerations
<!-- Address any security implications -->
- [ ] No security implications
- [ ] Security implications addressed:
- Input validation reviewed
- Error handling doesn't expose sensitive information
- Authentication/authorization considered
- Dependencies scanned for vulnerabilities
## Breaking Changes
<!-- If this is a breaking change, describe the impact and migration path -->
- [ ] No breaking changes
- [ ] Breaking changes (describe below):
### Migration Guide
<!-- Provide migration instructions for breaking changes -->
## Documentation
<!-- Check all that apply -->
- [ ] Code is self-documenting with clear variable/function names
- [ ] Added/updated JSDoc comments for new functions
- [ ] README updated (if user-facing changes)
- [ ] CONTRIBUTING.md updated (if development process changes)
- [ ] API documentation updated (if API changes)
## Code Quality
<!-- Confirm code quality standards -->
- [ ] Code follows existing style and conventions
- [ ] `npm run validate` passes (format, lint, type-check, test)
- [ ] No new TypeScript errors
- [ ] No new ESLint warnings
- [ ] Pre-commit hooks pass
## Performance Impact
<!-- Describe any performance implications -->
- [ ] No performance impact
- [ ] Performance improved
- [ ] Performance impact acceptable because:
## Deployment Considerations
<!-- Any special deployment considerations -->
- [ ] No special deployment considerations
- [ ] Environment variables changed
- [ ] Dependencies added/updated
- [ ] Configuration changes required
- [ ] Database migrations required
## Screenshots
<!-- Include screenshots for UI changes or visual improvements -->
| Before | After |
| ------ | ----- |
| | |
## Additional Context
<!-- Any additional information that reviewers should know -->
## Checklist
<!-- Final checklist before requesting review -->
- [ ] I have read the [CONTRIBUTING.md](../CONTRIBUTING.md) guidelines
- [ ] I have followed the [RULES.md](../RULES.md) development rules
- [ ] My code follows the project's coding standards
- [ ] 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
- [ ] 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
- [ ] Any dependent changes have been merged and published
## Questions for Reviewers
<!-- Any specific questions or areas you'd like feedback on -->
---
**Note**: Please ensure all CI checks pass before requesting review. If you need help with any failing checks, please ask in the comments.
