feat(git-publish-workflow): feat(git-publish-workflow): handle multi-branch repsitories

Verify branching tree and select the proper PR base/target to reflect
the branching order.

skills/date-time/SKILL.md

@@ -3,6 +3,7 @@ name: date-time
 description: Retrieves the exact current date and time for time-sensitive queries, scheduling, duration calculations, and validating chronological context.
 version: 1.0.0
 user-invocable: true
+author: Rootiest
 ---
 
 # Current Date and Time Retrieval

skills/docs-sync-audit/SKILL.md

@@ -3,6 +3,7 @@ name: docs-sync-audit
 description: Analyzes repository delta since the last documentation update and synchronizes the Single Source of Truth (docs/, wiki, or README) with the current codebase state.
 version: 1.3.0
 user-invocable: true
+author: Rootiest
 ---
 
 # Documentation Synchronization & Audit Skill

skills/git-publish-workflow/SKILL.md

@@ -1,24 +1,30 @@
 ---
 name: git-publish-workflow
-description: Automates branching, conventional commits, testing, and PR creation for uncommitted or staged work.
+description: Automates branching, conventional commits, testing, and PR creation for uncommitted or staged work. Handles both independent and stacked PRs.
-version: 1.1.0
+version: 1.2.0
 user-invocable: true
+author: Rootiest
 ---
 
 # Git Publish & PR Workflow
 
 ## **Objective**
-To provide a hands-off, end-to-end automation for moving local changes into a formal Pull Request, ensuring code quality through automated and manual verification steps.
+To provide a hands-off, end-to-end automation for moving local changes into a formal Pull Request, ensuring code quality through automated and manual verification steps, while intelligently routing Stacked PRs.
 
 ## **Execution Protocol**
 
-### **Phase 1: Scope Determination**
+### **Phase 1: Scope & Base Determination**
-Before execution, check the git index to determine the work boundary:
+Before execution, check the local git state:
-1. **Case A (Partial):** If staged changes exist, operate **ONLY** on staged changes.
+1. **Scope Check**: Determine the work boundary:
-2. **Case B (Full):** If no changes are staged, operate on **ALL** modified/untracked files.
+   * **Case A (Partial):** If staged changes exist, operate **ONLY** on staged changes.
+   * **Case B (Full):** If no changes are staged, operate on **ALL** modified/untracked files.
+2. **Base Branch Detection**: Identify the currently checked-out branch.
+   * **Independent PR**: If the current branch is `main` (or `master`), the new branch will be based on `main`. The PR target will be `main`.
+   * **Stacked PR**: If the current branch is a feature branch (e.g., `feat-a`), assume the new changes are dependent. The new branch will be created from the current branch. The PR target will be the current feature branch (NOT `main`).
+   * *Safety Check*: If creating a Stacked PR, output a brief terminal message stating: "Detected active feature branch. Stacking new PR on top of `[current-branch-name]`."
 
 ### **Phase 2: The "Safe-Commit" Sequence**
-1. **Branching**: Generate a `kebab-case` branch name (e.g., `feat-auth-logic` or `fix-header-css`).
+1. **Branching**: Generate a `kebab-case` branch name (e.g., `feat-auth-logic` or `fix-header-css`) based off the branch determined in Phase 1.
 2. **Naming**: Use **Conventional Commits** for the message (e.g., `feat(ui): add logout button`).
 3. **Verification**: 
    * Identify the project type (e.g., Rust/Cargo, Python/Poetry, Node/NPM).
@@ -26,8 +32,8 @@ Before execution, check the git index to determine the work boundary:
    * **Abort Policy**: If verification fails, stop the sequence and report the error. Do not push.
 
 ### **Phase 3: Remote Integration**
-1. **Push**: Upload the branch to `origin`.
+1. **Push**: Upload the new branch to `origin`.
-2. **PR Creation**: Open a Pull Request targeting the default branch (usually `main` or `master`).
+2. **PR Creation**: Open a Pull Request targeting the base branch determined in Phase 1 (either `main` or the parent feature branch).
 3. **Documentation**: Populate the PR description with:
    * **Summary**: A high-level overview of "Why" and "What."
    * **Manual Verification Checklist**: Provide a Markdown list (`- [ ]`) of 3-5 tactical steps for a human to verify the change in a live environment.

skills/readme-sync-audit/SKILL.md

@@ -3,6 +3,7 @@ name: readme-sync-audit
 description: Analyzes repository delta since the last documentation update and synchronizes the README.md with the current codebase state.
 version: 1.2.0
 user-invocable: true
+author: Rootiest
 ---
 
 # README Synchronization & Audit Skill

skills/ship-it/SKILL.md

@@ -3,6 +3,7 @@ name: ship-it
 description: Runs a comprehensive pre-flight audit, syncs the README, and publishes the changes to a new PR.
 version: 1.0.0
 user-invocable: true
+author: Rootiest
 ---
 
 # /ship-it

skills/systematic-enumeration/SKILL.md

@@ -3,6 +3,7 @@ name: systematic-enumeration
 description: Forces element-by-element verification for finite sets to prevent counting errors.
 version: 1.0.0
 user-invocable: true
+author: Rootiest
 ---
 
 # Systematic Enumeration & Verification Skill

skills/technical-devlog-scribe/SKILL.md

@@ -3,6 +3,7 @@ name: technical-devlog-scribe
 description: Generates a highly structured, objective technical summary of a development session.
 version: 1.0.0
 user-invocable: true
+author: Rootiest
 ---
 
 # SKILL: Technical Devlog Scribe