Back to skills
extension
Category: Development & EngineeringNo API key required

pr-packaging

Package changes into a well-documented pull request. Use before submitting PRs.

personAuthor: jakexiaohubgithub

PR Packaging

Aggregate design artifacts and review findings into a comprehensive PR description.

Process

  1. Summarize what changed and why
  2. Document implementation approach
  3. Include testing performed
  4. Note review findings and resolutions
  5. Flag breaking changes and follow-ups

Output

Create PR description using the template in templates/pr-description.md.

Tips

  • Link to related issues/tickets
  • Highlight breaking changes prominently
  • Include test commands for reviewers
  • Note any deploy considerations
  • List follow-up tasks