- 🐛 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
- 🔧 Refactoring (no functional changes, no api changes)
- 🎨 Style changes (formatting, missing semi colons, etc; no code changes)
- 🧪 Test changes (adding missing tests, refactoring tests; no production code changes)
- 🔨 Build/CI changes (changes to build process or CI configuration)
- Unit tests added/updated
- Integration tests added/updated
- Storybook stories added/updated
- Accessibility tests pass
- Visual regression tests pass
- Manual testing completed
- Bundle size increase is within acceptable limits (< 10KB gzipped)
- No bundle size increase
- Bundle size decreased
<!-- Paste the output of `pnpm size-limit` here -->
- No breaking changes
- Breaking changes documented below
- README updated (if needed)
- CONTRIBUTING.md updated (if needed)
- Storybook documentation updated
- TypeScript types documented
- Changelog entry added (via changeset)
- New stories added for new components
- Existing stories updated for modified components
- All stories render without errors
- Interactive examples work correctly
- Components are keyboard navigable
- Proper ARIA labels and roles added
- Color contrast meets WCAG standards
- Screen reader testing completed
- axe-core tests pass
- Code follows project style guidelines
- Self-review of code completed
- Code is well-commented, particularly in hard-to-understand areas
- No console.log statements left in production code
- No TODO comments without associated issues
- TypeScript types are properly defined
- Error handling is appropriate
- ESLint passes without errors
- Prettier formatting applied
- TypeScript compilation successful
- No new TypeScript errors introduced
- No new dependencies added
- New dependencies justified and documented
- Dependencies updated to latest secure versions
- No unused dependencies
- No security vulnerabilities introduced
- Sensitive data properly handled
- Input validation implemented where needed
- Changes work in development environment
- Changes work in production-like environment
- No environment-specific configurations needed
- Closes #
- Fixes #
- Resolves #
- Related to #
- Depends on #
- Blocks #
- Code is readable and well-structured
- Logic is sound and efficient
- Error handling is appropriate
- Security considerations addressed
- Performance impact considered
- Test coverage is adequate
- Tests are meaningful and test the right things
- Edge cases are covered
- Tests pass consistently
- Documentation is accurate and complete
- Examples are clear and helpful
- API documentation is up to date
- UI/UX follows design system guidelines
- Responsive design works correctly
- Accessibility requirements met
- Visual design is consistent
- All automated checks pass
- Manual testing completed
- Ready for merge
Note for Reviewers: Please ensure all checklist items are completed before approving. If any items are not applicable, mark them as complete and note why in your review comments.