Generate Pr Description

Overview

Create a comprehensive pull request description based on the changes in this branch and format it as proper markdown for use in a GitHub PR description.

Steps

1. Summary

• Provide a clear, concise summary of what this PR accomplishes

1. Changes Made

• List the key changes made in this PR
• Include both code and non-code changes
• Highlight any breaking changes

1. Testing

• Describe how the changes were tested
• Include any new test cases added
• Note any manual testing performed

1. Related Issues

• Link to any related issues or tickets
• Use closing keywords if this PR resolves issues

1. Additional Notes

• Any deployment considerations
• Follow-up work required
• Notes for reviewers

Generate PR Description Checklist

• [ ] Provided clear, concise summary of what this PR accomplishes
• [ ] Listed all key changes made in this PR
• [ ] Highlighted any breaking changes
• [ ] Described how the changes were tested
• [ ] Included any new test cases added
• [ ] Noted any manual testing performed
• [ ] Linked to any related issues or tickets
• [ ] Included any deployment considerations
• [ ] Noted any follow-up work required
• [ ] Formatted as proper markdown for GitHub PR

Guardrails

• Always include a test plan describing how the changes were verified.
• Use Conventional Commits style for the PR title when appropriate.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: emaraschio
• Source: emaraschio/cursor-commands
• License: MIT
• Homepage: https://github.com/emaraschio/cursor-commands#readme

Install and usage instructions live in the source repository linked above.