📝[Fix]: Enhance repository handling instructions across prompts for clarity and consistency

Author: MariusStorhaug

.github/prompts/implement.prompt.md

@@ -25,14 +25,14 @@ $ARGUMENTS
 
 1. **Set Implementing label immediately**
    - **Determine target repository**:
-     - Run `git remote -v` to check configured remotes
+     - Run `git remote -v` to check configured remotes.
      - **If `upstream` remote exists**: Fork mode
-       - Parse the upstream URL to extract owner and repo name
-       - Example: `upstream https://github.com/PSModule/Utilities.git` → owner: `PSModule`, repo: `Utilities`
-       - Use `upstream_owner/upstream_repo` for all GitHub operations
+       - 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
-       - Parse the origin URL to extract owner and repo name
-       - Use `origin_owner/origin_repo` for all GitHub operations
+       - 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.
    - Get the issue number associated with the current feature branch.
    - **Add `Implementing` label** to the issue and PR immediately in the target repository.
    - **Remove `Planning` label** from the issue and PR.

.github/prompts/plan.prompt.md

@@ -20,14 +20,14 @@ Given the implementation details provided as an argument, do this:
 
 1. **Set Planning label immediately**:
    - **Determine target repository**:
-     - Run `git remote -v` to check configured remotes
+     - Run `git remote -v` to check configured remotes.
      - **If `upstream` remote exists**: Fork mode
-       - Parse the upstream URL to extract owner and repo name
-       - Example: `upstream https://github.com/PSModule/Utilities.git` → owner: `PSModule`, repo: `Utilities`
-       - Use `upstream_owner/upstream_repo` for all GitHub operations
+       - 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
-       - Parse the origin URL to extract owner and repo name
-       - Use `origin_owner/origin_repo` for all GitHub operations
+       - 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.
    - Get the issue number associated with the current feature branch
    - **Add 'Planning' label** to the issue immediately in the target repository
    - **Remove 'Specification' label** from the issue
@@ -85,14 +85,14 @@ Given the implementation details provided as an argument, do this:
 
 8. Create or update a Pull Request:
    - **Determine workflow mode and target repository**:
-     - Run `git remote -v` to check configured remotes
-     - **If `upstream` remote exists** (fork mode):
-       - Parse the upstream URL to extract owner and repo name
-       - Example: `upstream https://github.com/PSModule/Utilities.git` → owner: `PSModule`, repo: `Utilities`
-       - Use `upstream_owner/upstream_repo` for all GitHub operations
-     - **If only `origin` remote exists** (local mode - default):
-       - Parse the origin URL to extract owner and repo name
-       - Use `origin_owner/origin_repo` for all GitHub operations
+     - Run `git remote -v` to check configured remotes.
+     - **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.
    - **Determine PR operation** (create vs update):
      - If PR already exists for this branch, UPDATE it
      - If no PR exists, CREATE a new one

.github/prompts/specify.prompt.md

@@ -21,14 +21,14 @@ The text the user typed after `/specify` in the triggering message **is** the fe
 Given that feature description, do this:
 
 1. **Detect repository mode**:
-   - Run `git remote -v` to check configured remotes
-   - **If `upstream` remote exists**: Fork mode detected
-     - Parse the upstream URL to extract owner and repo name
-     - Example: `upstream https://github.com/PSModule/Utilities.git` → owner: `PSModule`, repo: `Utilities`
-     - Inform user: "Fork contribution detected. Issues and PRs will target `<upstream_owner>/<upstream_repo>`"
-   - **If only `origin` remote exists**: Origin mode (default)
-     - Parse the origin URL to extract owner and repo name
-     - Use `origin_owner/origin_repo` for all GitHub operations
+   - Run `git remote -v` to check configured remotes.
+   - **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.
 
 2. Analyze the feature description and generate a concise, descriptive branch name:
    - Extract the core concept/action from the description (2-4 words maximum)
@@ -69,8 +69,8 @@ Given that feature description, do this:
 
 6. Create or update a GitHub issue for this feature:
    - **Use target repository determined in step 1**:
-     - If fork mode: Use `upstream_owner/upstream_repo` for all GitHub operations
-     - If origin mode: Use `origin_owner/origin_repo` for all GitHub operations
+     - If fork mode: Use `upstream` owner/repo for all GitHub operations (PRs, Issues, labels)
+     - If origin mode: Use `origin` owner/repo for all operations (both git push and GitHub operations)
    - **Generate the issue title** in format `<Icon> [Type]: <Feature name>` where:
      - Icon: 📖 (Docs), 🪲 (Fix), ⚠️ (Security fix), 🩹 (Patch), 🚀 (Feature/Minor), 🌟 (Breaking change/Major)
      - Type: Docs, Fix, Patch, Feature, or Breaking change

.github/prompts/tasks.prompt.md

@@ -83,14 +83,14 @@ $ARGUMENTS
 
 8. Update the Pull Request description:
    - **Determine workflow mode and target repository**:
-     - Run `git remote -v` to check configured remotes
-     - **If `upstream` remote exists** (fork mode):
-       - Parse the upstream URL to extract owner and repo name
-       - Example: `upstream https://github.com/PSModule/Utilities.git` → owner: `PSModule`, repo: `Utilities`
-       - Use `upstream_owner/upstream_repo` for all GitHub operations
-     - **If only `origin` remote exists** (local mode - default):
-       - Parse the origin URL to extract owner and repo name
-       - Use `origin_owner/origin_repo` for all GitHub operations
+     - Run `git remote -v` to check configured remotes.
+     - **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.
    - Append or update the tasks.md content in the existing PR description
    - Format tasks with checkboxes for each task phase:
      * Setup: `- [ ] T001: Task description`