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.

.gitignore

@@ -1,7 +1,114 @@
-# AI sessions and project overviews
-.remember
-.gemini*
-.claude*
-CLAUDE.md
-GEMINI.md
-AGENTS.md
+# id: gi-patterns-54143085ec229f3cf907a5aa2a8fcade
+# Created by https://www.toptal.com/developers/gitignore/api/linux
+# Edit at https://www.toptal.com/developers/gitignore?templates=linux
+
+### Linux ###
+*~
+
+# temporary files which can be created if a process still has a handle open of a deleted file
+.fuse_hidden*
+
+# KDE directory preferences
+.directory
+
+# Linux trash folder which might appear on any partition or disk
+.Trash-*
+
+# .nfs files are created when an open file is removed but is still being accessed
+.nfs*
+
+# End of https://www.toptal.com/developers/gitignore/api/linux
+
+# id: gitig-boilerplate-92f3a89d2c63f6a381be8bebd1862de5
+#   ╭──────────────────────────────────────────────────────────╮
+#   │              GitIgnore Boilerplate Template              │
+#   ╰──────────────────────────────────────────────────────────╯
+#
+#   ──────────────────── OS-Generated Files ────────────────────
+# automatic backup files created by some editors (e.g., Vim, Emacs)
+*~
+
+# temporary files created if a process still has a handle to a deleted file
+.fuse_hidden*
+
+# KDE directory preferences
+.directory
+
+# MacOS junk
+.DS_Store
+Thumbs.db
+
+# Linux trash folder which might appear on any partition or disk
+.Trash-*
+
+# files created when an open file is removed but is still being accessed
+.nfs*
+
+#   ─────────────────── Debug/Temporary/Testing ────────────────
+# Matches OLD / .OLD
+[Oo][Ll][Dd]/
+.[Oo][Ll][Dd]/
+
+# Matches DISABLE / .DISABLE
+[Dd][Ii][Ss][Aa][Bb][Ll][Ee]/
+.[Dd][Ii][Ss][Aa][Bb][Ll][Ee]/
+
+# Matches DISABLED / .DISABLED
+[Dd][Ii][Ss][Aa][Bb][Ll][Ee][Dd]/
+.[Dd][Ii][Ss][Aa][Bb][Ll][Ee][Dd]/
+
+# Matches DEBUG / .DEBUG
+[Dd][Ee][Bb][Uu][Gg]/
+.[Dd][Ee][Bb][Uu][Gg]/
+
+# Matches TMP / .TMP
+[Tt][Mm][Pp]/
+.[Tt][Mm][Pp]/
+
+# Matches TEMP / .TEMP
+[Tt][Ee][Mm][Pp]/
+.[Tt][Ee][Mm][Pp]/
+
+# Matches TEMPORARY / .TEMPORARY
+[Tt][Ee][Mm][Pp][Oo][Rr][Aa][Rr][Yy]/
+.[Tt][Ee][Mm][Pp][Oo][Rr][Aa][Rr][Yy]/
+
+# Matches TESTING / .TESTING
+[Tt][Ee][Ss][Tt][Ii][Nn][Gg]/
+.[Tt][Ee][Ss][Tt][Ii][Nn][Gg]/
+
+#   ─────────────────── AI Sessions and Rules ──────────────────
+# Matches CLAUDE.md, .claud*, etc.
+[Cc][Ll][Aa][Uu][Dd][Ee].[Mm][Dd]
+.[Cc][Ll][Aa][Uu][Dd]*
+
+# Matches GEMINI.md, .gemin*, etc.
+[Gg][Ee][Mm][Ii][Nn][Ii].[Mm][Dd]
+.[Gg][Ee][Mm][Ii][Nn]*
+
+# Matches ANTIGRAVITY.md, .antigrav*, etc.
+[Aa][nN][Tt][Ii][Gg][Rr][Aa][Vv][Ii][Tt][Yy].[Mm][Dd]
+.[Aa][Nn][Tt][Ii][Gg][Rr][Aa][Vv]*
+
+# Matches AGENTS.md, .remember, etc.
+[Aa][Gg][Ee][Nn][Tt][Ss].[Mm][Dd]
+.[Rr][Ee][Mm][Ee][Mm][Bb][Ee][Rr]
+
+#   ──────────────────── Planning Artifacts ───────────────────
+# Catalog files generated by pre-implementation analysis passes
+.superpowers
+docs/superpowers
+docs/specs
+
+# ──────────────────────────────────────────────────────────────
+
+#   ──────────────── Added by agents-init ──────────────────
+#   agents-init --agents
+AGENTS/
+#   ────────────────────────────────────────────────────────
+
+#   ──────────────── Added by agents-init ──────────────────
+#   agents-init --plugins
+docs/plans
+docs/devlogs
+#   ────────────────────────────────────────────────────────

README.md

@@ -12,6 +12,9 @@ Skills are plain Markdown files. The included `install.sh` script handles discov
   - [systematic-enumeration](#systematic-enumeration)
   - [git-publish-workflow](#git-publish-workflow)
   - [readme-sync-audit](#readme-sync-audit)
+  - [docs-sync-audit](#docs-sync-audit)
+  - [date-time](#date-time)
+  - [technical-devlog-scribe](#technical-devlog-scribe)
   - [ship-it](#ship-it)
 - [Installation](#installation)
   - [Quick Install (curl)](#quick-install-curl)
@@ -67,13 +70,49 @@ Three-phase execution:
 
 ---
 
+### `docs-sync-audit`
+
+**Purpose:** Keep documentation accurate by aligning the project's Single Source of Truth (SSoT) with the current state of the codebase.
+
+Unlike `readme-sync-audit`, this skill first discovers the documentation root. If a dedicated `docs/`, `wiki/`, or site config (e.g. `mkdocs.yml`) exists, it is treated as the SSoT and receives the detailed updates; the `README.md` is then kept as a high-level landing page that links into it. If no docs directory exists, it falls back to `README.md` as the SSoT.
+
+Three-phase execution:
+
+1. **Delta Analysis** — locate the last commit that touched the SSoT, diff all code changes to `HEAD`, and extract undocumented environment variables, CLI flags, or API changes.
+2. **Pruning & Update Audit** — route detailed changes to the correct files, remove stale steps, correct versions and paths, and synthesize docs for new features.
+3. **Structural Integrity Check** — verify Quick Start commands, configuration keys, and usage examples still match the implementation.
+
+**Use when:** you say "Update the docs," "Sync the wiki," or invoke `/docs-sync-audit`.
+
+---
+
+### `date-time`
+
+**Purpose:** Retrieve the exact, real-time current date and time when a task depends on the present moment.
+
+The skill runs the system `date` command rather than guessing, then uses the result for time-sensitive reasoning.
+
+**Use when:** the request asks for the current date/time, uses relative expressions ("today", "next week", "recently"), or needs an age, duration, countdown, or check of whether an event has already occurred.
+
+---
+
+### `technical-devlog-scribe`
+
+**Purpose:** Produce a dense, objective technical summary of a development session as a durable historical record optimized for future context loading.
+
+The skill writes a structured Markdown file to `AGENTS/devlogs/<kebab-case-short-description>.md`, with YAML frontmatter (date, title, tags, status) followed by the session summary. It relies strictly on what happened in the session — no hallucinated external constraints — and avoids conversational filler.
+
+**Use when:** you say "session wrap-up," "write a devlog," "done for the day," or want an auditable record of what changed and why.
+
+---
+
 ### `ship-it`
 
 **Purpose:** Run a comprehensive pre-flight audit and publish changes to a new PR in a single command.
 
 Two sequential phases — Phase 2 is blocked until Phase 1 succeeds:
 
-1. **Documentation Sync & Code Audit** — acts as `/readme-sync-audit`: scans all file changes since the last README edit, updates the README to match the current codebase, and audits code files for syntax errors or regressions. **Halts the entire workflow** if any breaking issue is found.
+1. **Documentation Sync & Code Audit** — acts as `/docs-sync-audit`: scans all file changes since the last documentation edit, updates the docs/README to match the current codebase, and audits code files for syntax errors or regressions. **Halts the entire workflow** if any breaking issue is found.
 2. **Git Publish Workflow** — acts as `/git-publish-workflow`: creates a descriptively named branch, commits all pending changes (including the README updates from Phase 1), pushes to the remote, and opens a Pull Request against `main`.
 
 **Use when:** you say "Ship this," "Publish my changes," or invoke `/ship-it`.

descriptions.json

@@ -4,5 +4,6 @@
   "git-publish-workflow": "Automate the full lifecycle from uncommitted local work to an open Pull Request, with built-in quality gates.",
   "readme-sync-audit": "Keep README.md accurate by programmatically aligning it with the current state of the codebase.",
   "ship-it": "Run a comprehensive pre-flight audit and publish changes to a new PR in a single command.",
-  "systematic-enumeration": "Eliminate counting and membership errors via explicit set enumeration and atomic element testing."
+  "systematic-enumeration": "Eliminate counting and membership errors via explicit set enumeration and atomic element testing.",
+  "technical-devlog-scribe": "Generates a highly structured, objective technical summary of a development session."
 }

skills/date-time/SKILL.md

@@ -1,4 +1,12 @@
-# Skill Name: Current Date and Time Retrieval
+---
+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
 
 ## Purpose
 Enables the assistant to retrieve the exact, real-time current date and time when addressing time-sensitive queries, scheduling tasks, calculating durations, or validating chronological context.

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.
-version: 1.1.0
+description: Automates branching, conventional commits, testing, and PR creation for uncommitted or staged work. Handles both independent and stacked PRs.
+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**
-Before execution, check the git index to determine the work boundary:
-1. **Case A (Partial):** If staged changes exist, operate **ONLY** on staged changes.
-2. **Case B (Full):** If no changes are staged, operate on **ALL** modified/untracked files.
+### **Phase 1: Scope & Base Determination**
+Before execution, check the local git state:
+1. **Scope Check**: Determine the work boundary:
+   * **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`.
-2. **PR Creation**: Open a Pull Request targeting the default branch (usually `main` or `master`).
+1. **Push**: Upload the new branch to `origin`.
+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

@@ -1,5 +1,12 @@
-Name: /ship-it
-Description: Run a comprehensive pre-flight audit, sync the README, and publish the changes to a new PR.
+---
+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
 
 Instructions:
 Execute the following two phases sequentially. Do not proceed to Phase 2 unless Phase 1 completes successfully.

skills/systematic-enumeration/SKILL.md

@@ -1,9 +1,9 @@
 ---
-name: Systematic Enumeration
+name: systematic-enumeration
 description: Forces element-by-element verification for finite sets to prevent counting errors.
-version: 1.0
+version: 1.0.0
 user-invocable: true
-disable-model-invocation: false
+author: Rootiest
 ---
 
 # Systematic Enumeration & Verification Skill

skills/technical-devlog-scribe/SKILL.md

@@ -0,0 +1,32 @@
+---
+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
+
+## Description
+Generates a comprehensive, highly structured technical summary of a development session. This skill acts as an objective technical scribe, producing a reliable historical record optimized for future context loading and maintaining a single source of truth for project evolution.
+
+## System Directives
+* **Tone & Style:** Maintain an objective, dense, and highly technical tone. Avoid conversational filler or fluff. 
+* **Accuracy:** Rely strictly on the actions, code snippets, and decisions discussed within the current session. Do not hallucinate external constraints.
+* **File Routing:** The output must be saved directly to `AGENTS/devlogs/<kebab-case-short-description>.md`. Ensure the filename is concise but descriptive (e.g., `AGENTS/devlogs/oauth2-token-refresh-fix.md`).
+
+## Required Output Structure
+
+The generated markdown file must adhere strictly to the following format:
+
+---
+**[START OF FILE FORMAT]**
+
+```yaml
+---
+date: YYYY-MM-DD
+title: <Clear, concise title>
+tags: [<relevant>, <tech>, <stack>, <tags>]
+status: <Complete | In-Progress | Blocked>
+---