pull_request_template.md

Summary

Closes #

---

Type of Change

• feat — new feature
• fix — bug fix
• docs — documentation only
• refactor — code restructure, no feature/fix
• perf — performance improvement
• test — adding or fixing tests
• chore — build, tooling, or dependency update
• ci — CI/CD changes
• Breaking change (existing functionality is affected)

---

Changes Made

---

How to Test

---

Screenshots / Recordings

---

Pre-Merge Checklist

Author

• Branch is up to date with main
• PR title follows Conventional Commits format: type(scope): description (#issue)
• All CI checks pass (lint, tests, build)
• Self-reviewed the diff — no debug logs, commented-out code, or accidental files
• No secrets or credentials committed

Code Quality

• Code follows the Code Style Guide
• No any types introduced (TypeScript)
• Error cases and edge cases are handled
• New logic is covered by tests (or existing tests updated)

Contracts (if applicable)

• Linked spec exists in .kiro/specs/
• cargo fmt --all and cargo clippy -- -D warnings pass
• cargo test passes

Documentation

• Inline comments / JSDoc updated where needed
• Relevant docs updated (README, guides, API spec)
• CHANGELOG updated for user-facing changes

---

Additional Notes