PULL_REQUEST_TEMPLATE.mdβ’2.94 kB
## π― Semantic Intent
**What semantic problem does this PR solve?**
Brief description of the semantic intent behind this change.
## π Description
**What changed and why?**
Detailed explanation of the changes and their business value.
## π Related Issues
Closes #(issue)
## ποΈ Type of Change
- [ ] π 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)
- [ ] β‘ Performance improvement
- [ ] π Security enhancement
- [ ] β
Test additions or updates
## π Architectural Impact
**Which layers are affected?**
- [ ] Domain Layer (`src/domain/`)
- [ ] Application Layer (`src/application/`)
- [ ] Infrastructure Layer (`src/infrastructure/`)
- [ ] Presentation Layer (`src/presentation/`)
- [ ] None (documentation, tests, etc.)
## β
Checklist
**Before submitting:**
- [ ] My code follows the semantic intent patterns
- [ ] I have added semantic documentation (WHY, not just WHAT)
- [ ] I have added tests that prove my fix/feature works
- [ ] All new and existing tests pass locally (`npm test`)
- [ ] TypeScript compilation succeeds (`npm run type-check`)
- [ ] Code is formatted (`npm run format`)
- [ ] I have updated the documentation (if applicable)
- [ ] My changes generate no new warnings
- [ ] I have reviewed my own code
- [ ] I have commented complex or non-obvious code
## π§ͺ Testing
**How has this been tested?**
Describe the tests you ran:
- [ ] Unit tests added/updated
- [ ] Integration tests (if applicable)
- [ ] Manual testing performed
**Test configuration:**
- Node.js version:
- OS:
- Wrangler version:
## πΈ Screenshots (if applicable)
Add screenshots for UI changes or visual improvements.
## π¨ Code Quality
**Semantic Intent Documentation:**
- [ ] All new functions include semantic intent comments
- [ ] Complex logic is explained with WHY comments
- [ ] Business rules are documented
**Architecture:**
- [ ] Changes maintain layer boundaries
- [ ] No infrastructure leaking into domain
- [ ] Dependency injection used where appropriate
## π Breaking Changes
**Does this PR introduce breaking changes?**
- [ ] No breaking changes
- [ ] Yes, breaking changes documented below
**If yes, describe migration path:**
```
// Migration example
```
## π Additional Context
Add any other context about the PR here.
## π€ Reviewer Notes
**Specific areas to review:**
- [ ] Semantic intent clarity
- [ ] Test coverage
- [ ] Performance implications
- [ ] Security considerations
---
**By submitting this PR, I confirm:**
- [ ] I have read and followed the [CONTRIBUTING.md](../CONTRIBUTING.md) guidelines
- [ ] My changes maintain semantic integrity
- [ ] I agree to the terms of the MIT License