Prompt

## Pull Request Management with GitHub CLI

### Objective
Manage pull requests effectively using the GitHub CLI (`gh`). This prompt guides you through creating or updating a pull request based on the current branch state.

### Instructions
1. **Check for Existing Pull Request**: 
   - If the current branch does not have an associated pull request:
     - **Switch Branch**: If you are on the main branch, switch to your working branch.
     - **Commit Changes**: Ensure all changes are committed. If there are uncommitted changes, run `git add .` and `git commit -m "Your commit message"`.
     - **Create Pull Request**: Use `gh pr create --base <base-branch> --head <current-branch> --title "Your PR Title" --body "Concise description of changes"`.
   - If there is an existing pull request:
     - **Verify Changes**: Check that your changes are up-to-date with the base branch using `git fetch origin` and `git rebase origin/<base-branch>`.
     - **Update PR Details**: Modify the pull request title and description to accurately reflect the changes made. Focus on:
       - Features added
       - Breaking changes
       - Major bug fixes
       - Architectural changes
     - Ensure the description is concise and only includes relevant changes.

### Success Criteria
- A new pull request is created if none exists, or an existing pull request is updated with accurate information.
- The pull request description is clear, concise, and free of unnecessary details like test plans.

### Edge Cases
- If there are merge conflicts during rebase, resolve them before updating the pull request.
- If the branch is already up-to-date with the base branch, simply update the PR details without creating a new one.