📝[Enhancement]: Clarify repository mode operations and improve PR creation steps in prompt documentation

Author: MariusStorhaug

.github/prompts/pr.prompt.md

@@ -26,8 +26,11 @@ $ARGUMENTS
 
 1. **Detect repository mode**:
    - Run `git remote -v` to check configured remotes.
-   - **If `upstream` remote exists**: Fork mode - use upstream owner/repo for all GitHub operations
-   - **If only `origin` remote exists**: Origin mode - use origin owner/repo for all GitHub operations
+   - **If `upstream` remote exists**: Fork mode
+     - Use `upstream` owner/repo for all GitHub operations (PRs, Issues, labels)
+     - Use `origin` for all git operations (push, fetch)
+   - **If only `origin` remote exists**: Origin mode
+     - Use `origin` owner/repo for all operations (both git push and GitHub operations)
    - Parse the URLs to extract owner and repo name: `https://github.com/<owner>/<repository>.git`.
    - If in doubt, ask the user to clarify which repository to target.
 
@@ -48,11 +51,11 @@ $ARGUMENTS
 3. **Get current branch information**:
    - Determine the current branch name
    - Verify there are changes to commit (if uncommitted changes exist, stage and commit them first)
-   - Push the branch to remote if not already pushed.
+   - Push the branch to `origin` remote if not already pushed (always push to origin, even in fork mode).
 
 4. **Retrieve linked issue information** (if available):
    - Attempt to find the GitHub issue number associated with the current branch
-   - If found, retrieve the issue title from the target repository
+   - If found, retrieve the issue title from the **target repository** (upstream in fork mode, origin otherwise)
    - Use the issue title as the PR title (with appropriate icon prefix)
    - If no issue is found, ask the user to provide one of the following:
      - the number of the issue to link to the PR
@@ -80,28 +83,29 @@ $ARGUMENTS
    - Avoid implementation details unless necessary for understanding
 
 7. **Create or update the pull request**:
-   - **Check if PR already exists** for this branch in the target repository
+   - **Check if PR already exists** for this branch in the **target repository** (upstream in fork mode, origin otherwise)
    - **If PR exists**: Update the title, description, and labels
-   - **If PR does not exist**: Create a new PR
-   - Set PR to target the default branch (main/master)
+   - **If PR does not exist**: Create a new PR from your fork's branch to the target repository's default branch
+   - In fork mode, the PR will be from `<fork-owner>:<branch>` to `<upstream-owner>:<default-branch>`
+   - Set PR to target the default branch (main/master) of the target repository
    - Open as a **draft PR** (or keep as draft if updating)
-   - **Use GitHub MCP tools** to perform these operations:
+   - **Use GitHub MCP tools** to perform these operations in the **target repository**:
      ```
-     # Create PR (if not exists)
+     # Create PR (if not exists) - owner/repo should be target repository
      mcp_github_github_create_pull_request
 
-     # Update PR (if exists)
+     # Update PR (if exists) - owner/repo should be target repository
      mcp_github_github_update_pull_request
 
-     # Add labels to PR
+     # Add labels to PR - owner/repo should be target repository
      mcp_github_github_add_labels_to_issue (PRs are issues in GitHub API)
      ```
 
 8. **Apply labels to the PR**:
    - Add the **change type label** based on the type specified (Major, Minor, Patch, Fix, or Docs)
    - For Fix type, add both `Fix` and `Patch` labels
    - If currently in a feature workflow phase (e.g., Planning, Implementation), also apply that phase label
-   - Use GitHub MCP to add labels in the target repository
+   - Use GitHub MCP to add labels in the **target repository** (upstream in fork mode, origin otherwise)
 
 9. **Confirm completion**:
    - Display the PR URL to the user
@@ -117,6 +121,9 @@ $ARGUMENTS
 - `/PR Patch` - Create a PR for small improvements
 
 **Notes**:
+- Changes are always pushed to `origin` remote
+- In fork mode, PRs and Issue operations are performed on the `upstream` repository
+- In origin mode, all operations use the `origin` repository
 - This command commits and pushes changes if there are uncommitted changes
 - The PR is always created as a draft to allow for review before marking as ready
 - Labels can be manually adjusted after PR creation if needed