@slamb2k/mad-skills 2.0.49 → 2.0.50

package/.claude-plugin/plugin.json

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

package/package.json

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

package/skills/brace/SKILL.md

@@ -308,17 +308,23 @@ unknown). Platform detection and all CLI/REST commands are in
 1. Detect platform from `git remote get-url origin`
 2. **GitHub:** Check existing protection via `gh api`. If unprotected, ask via
    AskUserQuestion:
-   - "Yes, require PR reviews (Recommended)" — require 1 approval, block force push
+   - "Yes, require PR reviews (team project — Recommended)" — require 1 approval, block force push + deletion
+   - "Yes, protect branch without review requirement (solo project)" — block force push + deletion, no reviewer gate so `/ship` squash-merges without `--admin`
    - "Skip" — leave unprotected
 3. **Azure DevOps:** Extract org/project from remote URL. Check existing
    policies via `az repos` CLI or REST fallback. If no minimum reviewer
-   policy, ask via AskUserQuestion (same options as GitHub).
+   policy, ask via AskUserQuestion:
+   - "Yes, require PR reviews (team project — Recommended)" — 1 approver, creator votes do not count
+   - "Yes, PR required, author can self-approve (solo project)" — same approver policy but `creator-vote-counts=true` so the author's own vote satisfies the gate
+   - "Skip" — no policy applied
 4. **Unknown platform:** Skip and report.
 
-If user accepts, apply using the procedures in
-`references/branch-protection-steps.md`.
+Apply the variant matching the user's choice using the procedures in
+`references/branch-protection-steps.md` (see "Apply protection — team
+project" vs "Apply protection — solo project" for each platform).
 
-Include result in the final report under a "🔒 Branch protection" section.
+Include result in the final report under a "🔒 Branch protection" section,
+labelled with the chosen variant (team / solo / skipped).
 
 ---
 

package/skills/brace/references/branch-protection-steps.md

@@ -30,7 +30,10 @@ gh api repos/{owner}/{repo}/branches/{default_branch}/protection
 ```
 404 = unprotected.
 
-### Apply protection
+### Apply protection — team project (reviewer gate)
+
+Requires 1 approving review before merge. Use when multiple humans work on
+the repo.
 
 ```bash
 gh api repos/{owner}/{repo}/branches/{default_branch}/protection \
@@ -42,6 +45,34 @@ gh api repos/{owner}/{repo}/branches/{default_branch}/protection \
   -F allow_deletions=false
 ```
 
+### Apply protection — solo project (no reviewer gate)
+
+Keeps force-push and deletion prevention but drops the reviewer
+requirement. Use when you are the only contributor — this is what makes
+`/ship` squash-merge succeed without `gh pr merge --admin`.
+
+The only difference from the team variant is the absence of
+`-f required_pull_request_reviews=...`:
+
+```bash
+gh api repos/{owner}/{repo}/branches/{default_branch}/protection \
+  -X PUT \
+  -f enforce_admins=false \
+  -f restrictions=null \
+  -f required_status_checks=null \
+  -F allow_force_pushes=false \
+  -F allow_deletions=false
+```
+
+**Migrating an existing team-project repo to solo:** if a reviewer policy
+is already in place, remove just that sub-rule without tearing down the
+rest of the protection:
+
+```bash
+gh api --method DELETE \
+  repos/{owner}/{repo}/branches/{default_branch}/protection/required_pull_request_reviews
+```
+
 ---
 
 ## Azure DevOps
@@ -94,7 +125,10 @@ curl -s -H "$AUTH" \
   | jq "[.value[] | select(.settings.scope[]?.refName == \"refs/heads/$default_branch\" and .settings.scope[]?.repositoryId == \"$REPO_ID\")]"
 ```
 
-### Create minimum reviewer policy
+### Create minimum reviewer policy — team project (reviewer gate)
+
+Use when multiple humans review each other's PRs. The PR author's own
+vote does not count toward the minimum approver count.
 
 **CLI:**
 ```bash
@@ -133,3 +167,24 @@ curl -s -X POST -H "$AUTH" -H "Content-Type: application/json" \
     }
   }"
 ```
+
+### Create minimum reviewer policy — solo project (author self-approve)
+
+Use when you are the only contributor. A PR is still required before
+merge, but `--creator-vote-counts true` means the author's own vote
+satisfies the 1-approver gate — no second human needed.
+
+**CLI:**
+```bash
+az repos policy approver-count create \
+  --org "$AZDO_ORG_URL" --project "$AZDO_PROJECT" \
+  --repository-id "$REPO_ID" --branch "$default_branch" \
+  --minimum-approver-count 1 \
+  --creator-vote-counts true \
+  --allow-downvotes false \
+  --reset-on-source-push true \
+  --blocking true --enabled true
+```
+
+**REST fallback:** same body as the team variant, but with
+`"creatorVoteCounts": true`.

package/skills/manifest.json

@@ -1,12 +1,12 @@
 {
-  "generated": "2026-04-20T02:26:55.864Z",
+  "generated": "2026-04-20T02:56:39.184Z",
   "count": 11,
   "skills": [
     {
       "name": "brace",
       "directory": "brace",
       "description": "'Initialize any project directory with a standard scaffold for AI-assisted development. Creates specs/ and context/ directories, a project CLAUDE.md with development workflow and guardrails, .gitignore, and branch protection. Recommends claude-mem for persistent memory. Idempotent — safe to run on existing projects. Triggers: \"init project\", \"setup brace\", \"brace\", \"initialize\", \"bootstrap\", \"scaffold\".'",
-      "lines": 424,
+      "lines": 430,
       "hasScripts": false,
       "hasReferences": true,
       "hasAssets": true,