@slamb2k/mad-skills 2.0.31 → 2.0.33

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "mad-skills",
   "description": "AI-assisted planning, development and governance tools",
-  "version": "2.0.31",
+  "version": "2.0.33",
   "author": {
     "name": "slamb2k",
     "url": "https://github.com/slamb2k"

package/agents/ship-analyzer.md

@@ -11,6 +11,21 @@ model: sonnet
 
 You are a senior engineer responsible for crafting high-quality git commits and pull requests. You read and understand code — not just diffs — to produce meaningful, accurate descriptions of what changed and why.
 
+## CRITICAL: Platform Awareness
+
+Your prompt will include a `PLATFORM` variable (`github` or `azdo`). You MUST
+use this to choose the correct CLI tool for PR creation:
+
+- **`PLATFORM: github`** → use `gh pr create`
+- **`PLATFORM: azdo`** → use `az repos pr create` (NEVER use `gh` — it will fail)
+
+If no PLATFORM variable is provided, detect it yourself from the remote URL:
+- `github.com` → github
+- `dev.azure.com` or `visualstudio.com` → azdo
+
+**NEVER try `gh` commands on an Azure DevOps repository.** The `gh` CLI only
+works with GitHub. Azure DevOps requires `az repos` / `az pipelines` commands.
+
 ## Core Principles
 
 1. **Read before writing** — Always read the actual diff AND relevant source files before composing commit messages. Never guess at intent from filenames alone.
@@ -74,11 +89,11 @@ When given a set of files to ship:
 4. **Push**
    - `git push -u origin <branch>`
 
-5. **Create PR**
+5. **Create PR** (use the PLATFORM variable — do NOT guess)
    - Read the full diff against main to write the PR description
-   - Detect platform from remote URL (github.com → GitHub, dev.azure.com/visualstudio.com → Azure DevOps)
-   - GitHub: Use `gh pr create` with HEREDOC body
-   - Azure DevOps: Use `az repos pr create --title "..." --description "..." --source-branch <branch> --target-branch <default> --output json`
+   - **If PLATFORM == github:** Use `gh pr create` with HEREDOC body
+   - **If PLATFORM == azdo:** Use `az repos pr create --title "..." --description "..." --source-branch <branch> --target-branch <default> --output json`
+   - **NEVER try `gh` on an Azure DevOps repo** — it will fail with "none of the git remotes configured for this repository point to a known GitHub host"
 
 6. **Report results** in the structured format requested by the caller
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@slamb2k/mad-skills",
-  "version": "2.0.31",
+  "version": "2.0.33",
   "description": "Claude Code skills collection — full lifecycle development tools",
   "type": "module",
   "repository": {

package/skills/manifest.json

@@ -1,5 +1,5 @@
 {
-  "generated": "2026-03-13T00:14:06.892Z",
+  "generated": "2026-03-13T08:31:55.875Z",
   "count": 10,
   "skills": [
     {
@@ -76,7 +76,7 @@
       "name": "ship",
       "directory": "ship",
       "description": "\"Ship changes through the full PR lifecycle. Use after completing feature work to commit, push, create PR, wait for checks, and merge. Handles the entire workflow: syncs with main, creates feature branch if needed, groups commits logically with semantic messages, creates detailed PR, monitors CI, fixes issues, squash merges, and cleans up. Invoke when work is ready to ship.\"",
-      "lines": 374,
+      "lines": 388,
       "hasScripts": false,
       "hasReferences": true,
       "hasAssets": false,

package/skills/ship/SKILL.md

@@ -91,6 +91,15 @@ fi
 Pass `{PLATFORM}` into all stage prompts. Each stage uses the appropriate
 CLI tool: `gh` for GitHub, `az repos`/`az pipelines` for Azure DevOps.
 
+**Display the detected platform to the user immediately after detection:**
+```
+⚙️ Platform: GitHub (github.com)
+```
+or:
+```
+⚙️ Platform: Azure DevOps ({AZDO_ORG}/{AZDO_PROJECT})
+```
+
 ---
 
 ## Pre-flight
@@ -312,7 +321,7 @@ attempt = 0
 while attempt < 2:
   CHECKS = run_watch()
   if CHECKS.status == "all_passed" or CHECKS.status == "no_checks":
-    break  → proceed to Stage 5
+    break  → proceed immediately to Stage 5 (do NOT ask user to confirm merge)
   attempt += 1
   run_fix(CHECKS.failing_checks)
   → loop back to watch
@@ -325,6 +334,11 @@ if attempt == 2 and still failing:
 
 ## Stage 5: Merge & Final Sync
 
+Once checks pass, **immediately proceed to merge — do not ask the user for
+confirmation.** The user invoked `/ship` expecting the full lifecycle; stopping
+to ask defeats the purpose. Squash merge and delete the source branch are the
+defaults (override via `--no-squash` and `--keep-branch` flags only).
+
 Launch **Bash subagent** (haiku — simple git + platform CLI commands):
 
 ```

package/skills/ship/references/stage-prompts.md

@@ -19,7 +19,11 @@ push to a feature branch, and create a pull request.
 
 Limit SHIP_REPORT to 15 lines maximum.
 
+CRITICAL — READ THIS FIRST:
 PLATFORM: {PLATFORM}
+Use ONLY the tools for this platform. GitHub = gh CLI. Azure DevOps = az repos CLI.
+NEVER use gh commands on an Azure DevOps repository — they WILL fail.
+
 USER INTENT: {USER_INTENT}
 
 FILES TO INCLUDE: {FILES_TO_INCLUDE}
@@ -364,6 +368,7 @@ FIX_REPORT:
 
 ```
 Merge the pull request and sync local {DEFAULT_BRANCH}.
+Do NOT ask the user for confirmation — proceed immediately.
 
 Limit LAND_REPORT to 10 lines maximum.