snapshot of https://github.com/ueberdosis/tiptap.git (main, 2026-09-15; blobs > 131072B omitted)

.github/instructions/PR.instructions.md

@@ -0,0 +1,43 @@
+---
+applyTo: '**'
+---
+
+When asked to write a pull request description, use the following template:
+
+```
+## Changes Overview
+
+<!-- Briefly describe your changes. -->
+
+## Implementation Approach
+
+<!-- Describe your approach to implementing these changes. Keep it concise. -->
+
+## Testing Done
+
+<!-- Explain how you tested these changes. Link to test scenarios or specs if relevant. -->
+
+## Verification Steps
+
+<!-- Describe steps reviewers can take to verify the functionality of your changes. -->
+
+## Additional Notes
+
+<!-- Add any other notes or screenshots about the PR here. -->
+
+## Checklist
+
+- [ ] I have created a [changeset](https://github.com/changesets/changesets) for this PR if necessary.
+- [ ] My changes do not break the library.
+- [ ] I have added tests where applicable.
+- [ ] I have followed the project guidelines.
+- [ ] I have fixed any lint issues.
+
+## Related Issues
+
+<!-- Link any related issues here -->
+```
+
+When generating the pull request description, ensure it is clear, concise, and follows the provided template. Focus on the key aspects of the changes made, how they were implemented, and how they can be verified.
+
+Make it as minimal as possible to convey the necessary information effectively without causing to much noise and making it hard to read.