git-pr-ai/dist/default-template.md

A tool to automatically extract JIRA ticket numbers from branch names and create GitHub/GitLab PRs

<!-- AI_TEMPLATE_START: This is a structured PR description template for AI processing -->

## Summary

<!-- AI_INSTRUCTION: Provide a clear, concise explanation of what changed and why. Focus on the business value and technical impact. -->

[Describe the main purpose and goals of this PR]

### Key Changes

<!-- AI_INSTRUCTION: List the most important changes made in this PR. Use bullet points for clarity. -->

- [Change 1: Brief description]
- [Change 2: Brief description]
- [Change 3: Brief description]

## Type of Change

<!-- AI_INSTRUCTION: Check ALL applicable boxes based on the code changes. Use [x] to mark selected items. -->

- [ ] 🐛 Bug fix (non-breaking change which fixes an issue)
- [ ] ✨ New feature (non-breaking change which adds functionality)
- [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] 📚 Documentation update
- [ ] ♻️ Refactoring (no functional changes)
- [ ] 🎨 Style/formatting changes
- [ ] 🧪 Test improvements
- [ ] 🔧 Configuration changes

## Test Plan

<!-- AI_INSTRUCTION: Provide specific testing instructions. Include both manual and automated testing steps. -->

### Manual Testing

- [Step 1: How to test this change]
- [Step 2: Expected behavior]
- [Step 3: Edge cases to verify]

## Breaking Changes

<!-- AI_INSTRUCTION: If this is a breaking change, provide detailed migration instructions. If no breaking changes, write "None" -->

[List any breaking changes and provide migration notes, or write "None" if not applicable]

## Checklist

<!-- AI_INSTRUCTION: Check ALL completed items. Ensure all items are addressed before marking as ready for review. -->

- [ ] 📝 Code follows the style guidelines
- [ ] 👀 Self-review has been performed
- [ ] 🧪 Tests have been added/updated
- [ ] 📖 Documentation has been updated

<!-- AI_TEMPLATE_END -->