Create (or Update) Pull Request

Process

1. Verify branch status

Check if the current branch has been pushed; if not, push it to origin.

• If the current branch is "main" or "master," confirm with the user whether this is intended before proceeding.

2. Analyze commits by logical themes

Instead of reviewing each commit chronologically, group commits by their logical themes and purposes. Think of commits as A → A' → B → A'' → B' being grouped into themes A and B rather than 5 separate items.

3. Understand the WHY

Focus on why these changes were needed, not just what was changed. If the business context or motivation is unclear, ask the user for clarification.

4. Draft the PR