Description — what to implement and the why/impact.
Clear pull request instructions help contributors follow project conventions, such as linking issues, ensuring Zod validation, and maintaining TypeScript strictness. Adding or refining a pull request template standardizes PR submissions.
Context & Requirements — background, constraints, design references, edge cases;
grounded in the actual repo (real files, stack, conventions).
- GitHub templates reside in
.github/pull_request_template.md (or .github/ISSUE_TEMPLATE/).
- Include checkboxes for running tests (
npm test), building (npm run build), and referencing the closed issue.
Acceptance Criteria — a checklist ("- [ ] ...") of specific, testable conditions that define "done".
Implementation Guidance — likely files/modules to touch (use real paths from the repo context) and a suggested approach, without over-prescribing.
- Likely files:
.github/pull_request_template.md
Testing & Validation — how the contributor should prove it works (tests to add/run, manual checks, screenshots for UI).
- Verify file existence and markdown formatting.
Submission Guidelines — must open a PR that includes "Closes #"; assignment is required before starting; follow the repo's existing style and conventions.
Wave complexity: Trivial
Description — what to implement and the why/impact.
Clear pull request instructions help contributors follow project conventions, such as linking issues, ensuring Zod validation, and maintaining TypeScript strictness. Adding or refining a pull request template standardizes PR submissions.
Context & Requirements — background, constraints, design references, edge cases;
grounded in the actual repo (real files, stack, conventions).
.github/pull_request_template.md(or.github/ISSUE_TEMPLATE/).npm test), building (npm run build), and referencing the closed issue.Acceptance Criteria — a checklist ("- [ ] ...") of specific, testable conditions that define "done".
.github/pull_request_template.md.Closes #...).Implementation Guidance — likely files/modules to touch (use real paths from the repo context) and a suggested approach, without over-prescribing.
.github/pull_request_template.mdTesting & Validation — how the contributor should prove it works (tests to add/run, manual checks, screenshots for UI).
Submission Guidelines — must open a PR that includes "Closes #"; assignment is required before starting; follow the repo's existing style and conventions.
Wave complexity: Trivial