pr-writer

Create pull requests following Sentry's engineering practices. Requires : GitHub CLI ( gh ) authenticated and available. Before creating a PR, ensure all changes are committed to a feature branch , not to the default branch. If on main or master , create a feature branch and move any uncommitted changes onto it before committing — a PR cannot be opened from the default branch against itself. If there are uncommitted changes, commit them on the feature branch before proceeding. Ensure: Review what will be included in the PR: Understand the scope and purpose of all changes before writing the description. Use this same structure whether you are opening a new PR or updating an existing PR body. When updating, rewrite the final PR body so it still matches this structure instead of appending ad hoc notes or preserving repository template sections.