bigpowers 2.7.3 → 2.7.4

package/.pi/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.7.3",
+  "version": "2.7.4",
   "description": "62 skills — 61 agent skills for spec-driven, test-first software development by solo developers",
   "keywords": [
     "pi-package"

package/.pi/prompts/commit-message.md

@@ -25,7 +25,8 @@ description: Reviews working-tree changes, then drafts a Conventional Commits ti
 3. **Classify for semantic release** — `fix` → patch, `feat` → minor, **breaking** → major.
 4. **Write the message** — `type(optional-scope)!: description` (see [REFERENCE.md](REFERENCE.md#message-format)). Use `!` or a `BREAKING CHANGE:` footer when behavior contracts change.
 5. **Note defensive-code categories touched** — from CONVENTIONS.md: Rate limit | Retry with backoff | Circuit breaker | Timeout | Graceful degradation
-6. **Deliver** — Output:
+6. **Note fix-ratio contribution** — Each `fix:` commit counts toward `metrics.commit_ratio.fix` in `specs/state.yaml`. After `release-branch`, `session-state` recalculates the ratio automatically. A high fix rate (>30%) triggers a deploy + smoke-test suggestion.
+7. **Deliver** — Output:
    - Proposed **full commit message** (title + optional body + footers).
    - **Release bump** this commit would drive: `patch` | `minor` | `major` | `none`.
    - Optional `git add …` and `git commit -m` instructions; do **not** run destructive git commands unless the user asked.

package/.pi/prompts/release-branch.md

@@ -19,11 +19,13 @@ Read `specs/state.yaml` key `workflow_mode` first (`team-pr` | `solo-git`). Fall
 
 | Mode | When | Ship path |
 |------|------|-----------|
-| **solo-local** | `workflow_mode: solo-git` (or `profiles/solo-git.md` present as fallback) | `bash scripts/land-branch.sh <branch> "<conventional message>"` |
+| **solo-local** | `workflow_mode: solo-git` (or `profiles/solo-git.md` present as fallback) | Auto-detect: if `scripts/land-branch.sh` exists → use it; else → fallback (see Step 5) |
 | **team-pr** | `workflow_mode: team-pr` (default) | `gh pr create` → `gh pr merge --squash` |
 
 If unsure and working alone, prefer **solo-local**.
 
+> **Auto-detect note:** The solo-local path first checks if `scripts/land-branch.sh` exists and is executable. If present, the script handles the full squash-merge workflow. If absent, the built-in fallback sequence runs instead.
+
 ## Process
 
 ### 1. Final verification
@@ -49,11 +51,42 @@ Options: **Release (solo-local)** / **Open PR** / **Keep branch** / **Discard**
 
 ### 5. Solo-local integrate
 
-Run `commit-message` to produce the squash commit subject, then:
+Run `commit-message` to produce the squash commit subject. Then auto-detect the integration path:
+
+**Path A — `scripts/land-branch.sh` exists (happy path):**
 ```bash
 bash scripts/land-branch.sh <task-slug> "feat(scope): description"
 ```
 
+**Path B — `scripts/land-branch.sh` missing (fallback):**
+```bash
+# Fallback: manual squash-merge when land-branch.sh is absent
+FEATURE_BRANCH=<task-slug>
+DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo main)
+
+# Ensure we're on the feature branch
+if [ "$(git branch --show-current)" != "$FEATURE_BRANCH" ]; then
+  git checkout "$FEATURE_BRANCH"
+fi
+
+# Checkout default branch and update
+git checkout "$DEFAULT_BRANCH"
+git pull --rebase origin "$DEFAULT_BRANCH" 2>/dev/null || git pull origin "$DEFAULT_BRANCH"
+
+# Squash-merge the feature branch
+git merge --no-ff "$FEATURE_BRANCH" -m "<conventional-commit-message>"
+
+# Push
+git push origin "$DEFAULT_BRANCH"
+
+# Clean up local feature branch
+git branch -d "$FEATURE_BRANCH"
+```
+
+**Report which path was taken.** Print exactly:
+- `"used land-branch.sh"` if Path A
+- `"used fallback merge (land-branch.sh not found)"` if Path B
+
 ### 6. Create PR (team-pr only)
 
 See [REFERENCE.md](REFERENCE.md) for the full PR body template and gh commands.
@@ -94,6 +127,12 @@ git checkout main && git status && pwd
 
 Report: "Branch released. Integrate mode: <solo-local|team-pr>. cwd: $(pwd) on $(git branch --show-current)."
 
+## Solo-local fallback detail
+
+The fallback sequence (Path B above) handles the "remote has moved" case with `git pull --rebase`. Use when `scripts/land-branch.sh` is absent.
+
+**Acceptance:** When fallback runs, main is updated, feature branch is deleted locally, and output states `"used fallback merge (land-branch.sh not found)"`.
+
 ## Handoff
 
 Gate: READY -> next: survey-context

package/.pi/prompts/session-state.md

@@ -69,30 +69,19 @@ Whenever a significant decision is made or a milestone is reached:
 
 ## State Write-Lock Protocol
 
-> **HARD GATE** — Before any write to `specs/state.yaml` or `specs/execution-status.yaml`, acquire `specs/state.yaml.lock`. Release it immediately after the write. A stale lock (>60s) may be force-released.
+> **HARD GATE** — Lock `specs/state.yaml.lock` before writes; stale (>60s) may be force-released.
 
-### Acquire
-
-1. Check if `specs/state.yaml.lock` exists.
-2. If it exists, read the agent ID and timestamp inside.
-3. If the lock is stale (>60s old), remove it and proceed.
-4. If the lock is fresh (<60s), wait 2s and retry (max 15 attempts = 30s).
-5. Write `agent_id: <name>\nacquired_at: <ISO-8601>` to `specs/state.yaml.lock`.
-
-### Release
-
-1. After the write to `state.yaml` or `execution-status.yaml` completes:
-2. `rm specs/state.yaml.lock`
-
-### Lock format (`specs/state.yaml.lock`)
+1. Check lock exists. If fresh (<60s), wait 2s retry (max 15). Stale → remove.
+2. Write `agent_id: <name>\nacquired_at: <ISO-8601>` to lock.
+3. After write, `rm specs/state.yaml.lock`.
 
+Lock format:
 ```yaml
 agent_id: session-state
 acquired_at: "2026-06-11T14:30:00Z"
 ```
 
 
-
 ## Operations
 
 ### show-state (absorbed)
@@ -139,6 +128,16 @@ handoff:
   next_skill: survey-context
 ```
 
+## Tracking commit ratio
+
+After `release-branch` lands, compute fix-to-feature ratio via:
+```bash
+FEAT_COUNT=$(git log main --oneline --grep="^feat" | wc -l | tr -d ' ')
+FIX_COUNT=$(git log main --oneline --grep="^fix" | wc -l | tr -d ' ')
+FIX_PCT=$((FIX_COUNT * 100 / (FEAT_COUNT + FIX_COUNT)))
+```
+Update `specs/state.yaml` `metrics.commit_ratio` with counts. If `fix_pct > 30%`, emit: `"High fix rate (N%) — deploy + smoke-test recommended"`.
+
 ## Anti-Patterns
 
 - **Duplicate Plan**: Don't copy `release-plan.yaml` or epic shards into `state.yaml`.

package/.pi/prompts/stocktake-skills.md

@@ -14,13 +14,14 @@ Audit SKILL.md catalog for drift, stale triggers, missing HARD GATEs, and INDEX
 | Mode | Scope |
 |------|-------|
 | **Quick Scan** | Skills changed since last tag or in current diff |
-| **Full** | All 58 skills per SKILL-INDEX.md |
+| **Full** | All 62 skills per SKILL-INDEX.md + catalog audit |
 
 ## Process
 
-1. Run mode; for each skill check: exists, verb-noun, <300 lines total, HARD GATE present, INDEX row matches.
-2. Write `specs/STOCKTAKE-<date>.md` with findings table (skill, issue, severity).
-3. Critical findings → `plan-work` story; cosmetic → `evolve-skill` candidate.
+1. Run `bash scripts/audit-catalog.sh` to verify pi/skills ↔ source SKILL.md sync. Mismatch is a critical finding.
+2. Run mode; for each skill check: exists, verb-noun, &lt;300 lines total, HARD GATE present, INDEX row matches.
+3. Write `specs/STOCKTAKE-<date>.md` with findings table (skill, issue, severity).
+4. Critical findings → `plan-work` story; cosmetic → `evolve-skill` candidate.
 
 ## Verify
 

package/.pi/skills/commit-message/SKILL.md

@@ -27,7 +27,8 @@ model: haiku
 3. **Classify for semantic release** — `fix` → patch, `feat` → minor, **breaking** → major.
 4. **Write the message** — `type(optional-scope)!: description` (see [REFERENCE.md](REFERENCE.md#message-format)). Use `!` or a `BREAKING CHANGE:` footer when behavior contracts change.
 5. **Note defensive-code categories touched** — from CONVENTIONS.md: Rate limit | Retry with backoff | Circuit breaker | Timeout | Graceful degradation
-6. **Deliver** — Output:
+6. **Note fix-ratio contribution** — Each `fix:` commit counts toward `metrics.commit_ratio.fix` in `specs/state.yaml`. After `release-branch`, `session-state` recalculates the ratio automatically. A high fix rate (>30%) triggers a deploy + smoke-test suggestion.
+7. **Deliver** — Output:
    - Proposed **full commit message** (title + optional body + footers).
    - **Release bump** this commit would drive: `patch` | `minor` | `major` | `none`.
    - Optional `git add …` and `git commit -m` instructions; do **not** run destructive git commands unless the user asked.

package/.pi/skills/release-branch/SKILL.md

@@ -21,11 +21,13 @@ Read `specs/state.yaml` key `workflow_mode` first (`team-pr` | `solo-git`). Fall
 
 | Mode | When | Ship path |
 |------|------|-----------|
-| **solo-local** | `workflow_mode: solo-git` (or `profiles/solo-git.md` present as fallback) | `bash scripts/land-branch.sh <branch> "<conventional message>"` |
+| **solo-local** | `workflow_mode: solo-git` (or `profiles/solo-git.md` present as fallback) | Auto-detect: if `scripts/land-branch.sh` exists → use it; else → fallback (see Step 5) |
 | **team-pr** | `workflow_mode: team-pr` (default) | `gh pr create` → `gh pr merge --squash` |
 
 If unsure and working alone, prefer **solo-local**.
 
+> **Auto-detect note:** The solo-local path first checks if `scripts/land-branch.sh` exists and is executable. If present, the script handles the full squash-merge workflow. If absent, the built-in fallback sequence runs instead.
+
 ## Process
 
 ### 1. Final verification
@@ -51,11 +53,42 @@ Options: **Release (solo-local)** / **Open PR** / **Keep branch** / **Discard**
 
 ### 5. Solo-local integrate
 
-Run `commit-message` to produce the squash commit subject, then:
+Run `commit-message` to produce the squash commit subject. Then auto-detect the integration path:
+
+**Path A — `scripts/land-branch.sh` exists (happy path):**
 ```bash
 bash scripts/land-branch.sh <task-slug> "feat(scope): description"
 ```
 
+**Path B — `scripts/land-branch.sh` missing (fallback):**
+```bash
+# Fallback: manual squash-merge when land-branch.sh is absent
+FEATURE_BRANCH=<task-slug>
+DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo main)
+
+# Ensure we're on the feature branch
+if [ "$(git branch --show-current)" != "$FEATURE_BRANCH" ]; then
+  git checkout "$FEATURE_BRANCH"
+fi
+
+# Checkout default branch and update
+git checkout "$DEFAULT_BRANCH"
+git pull --rebase origin "$DEFAULT_BRANCH" 2>/dev/null || git pull origin "$DEFAULT_BRANCH"
+
+# Squash-merge the feature branch
+git merge --no-ff "$FEATURE_BRANCH" -m "<conventional-commit-message>"
+
+# Push
+git push origin "$DEFAULT_BRANCH"
+
+# Clean up local feature branch
+git branch -d "$FEATURE_BRANCH"
+```
+
+**Report which path was taken.** Print exactly:
+- `"used land-branch.sh"` if Path A
+- `"used fallback merge (land-branch.sh not found)"` if Path B
+
 ### 6. Create PR (team-pr only)
 
 See [REFERENCE.md](REFERENCE.md) for the full PR body template and gh commands.
@@ -96,6 +129,12 @@ git checkout main && git status && pwd
 
 Report: "Branch released. Integrate mode: <solo-local|team-pr>. cwd: $(pwd) on $(git branch --show-current)."
 
+## Solo-local fallback detail
+
+The fallback sequence (Path B above) handles the "remote has moved" case with `git pull --rebase`. Use when `scripts/land-branch.sh` is absent.
+
+**Acceptance:** When fallback runs, main is updated, feature branch is deleted locally, and output states `"used fallback merge (land-branch.sh not found)"`.
+
 ## Handoff
 
 Gate: READY -> next: survey-context

package/.pi/skills/session-state/SKILL.md

@@ -71,30 +71,19 @@ Whenever a significant decision is made or a milestone is reached:
 
 ## State Write-Lock Protocol
 
-> **HARD GATE** — Before any write to `specs/state.yaml` or `specs/execution-status.yaml`, acquire `specs/state.yaml.lock`. Release it immediately after the write. A stale lock (>60s) may be force-released.
+> **HARD GATE** — Lock `specs/state.yaml.lock` before writes; stale (>60s) may be force-released.
 
-### Acquire
-
-1. Check if `specs/state.yaml.lock` exists.
-2. If it exists, read the agent ID and timestamp inside.
-3. If the lock is stale (>60s old), remove it and proceed.
-4. If the lock is fresh (<60s), wait 2s and retry (max 15 attempts = 30s).
-5. Write `agent_id: <name>\nacquired_at: <ISO-8601>` to `specs/state.yaml.lock`.
-
-### Release
-
-1. After the write to `state.yaml` or `execution-status.yaml` completes:
-2. `rm specs/state.yaml.lock`
-
-### Lock format (`specs/state.yaml.lock`)
+1. Check lock exists. If fresh (<60s), wait 2s retry (max 15). Stale → remove.
+2. Write `agent_id: <name>\nacquired_at: <ISO-8601>` to lock.
+3. After write, `rm specs/state.yaml.lock`.
 
+Lock format:
 ```yaml
 agent_id: session-state
 acquired_at: "2026-06-11T14:30:00Z"
 ```
 
 
-
 ## Operations
 
 ### show-state (absorbed)
@@ -141,6 +130,16 @@ handoff:
   next_skill: survey-context
 ```
 
+## Tracking commit ratio
+
+After `release-branch` lands, compute fix-to-feature ratio via:
+```bash
+FEAT_COUNT=$(git log main --oneline --grep="^feat" | wc -l | tr -d ' ')
+FIX_COUNT=$(git log main --oneline --grep="^fix" | wc -l | tr -d ' ')
+FIX_PCT=$((FIX_COUNT * 100 / (FEAT_COUNT + FIX_COUNT)))
+```
+Update `specs/state.yaml` `metrics.commit_ratio` with counts. If `fix_pct > 30%`, emit: `"High fix rate (N%) — deploy + smoke-test recommended"`.
+
 ## Anti-Patterns
 
 - **Duplicate Plan**: Don't copy `release-plan.yaml` or epic shards into `state.yaml`.

package/.pi/skills/stocktake-skills/SKILL.md

@@ -16,13 +16,14 @@ Audit SKILL.md catalog for drift, stale triggers, missing HARD GATEs, and INDEX
 | Mode | Scope |
 |------|-------|
 | **Quick Scan** | Skills changed since last tag or in current diff |
-| **Full** | All 58 skills per SKILL-INDEX.md |
+| **Full** | All 62 skills per SKILL-INDEX.md + catalog audit |
 
 ## Process
 
-1. Run mode; for each skill check: exists, verb-noun, <300 lines total, HARD GATE present, INDEX row matches.
-2. Write `specs/STOCKTAKE-<date>.md` with findings table (skill, issue, severity).
-3. Critical findings → `plan-work` story; cosmetic → `evolve-skill` candidate.
+1. Run `bash scripts/audit-catalog.sh` to verify pi/skills ↔ source SKILL.md sync. Mismatch is a critical finding.
+2. Run mode; for each skill check: exists, verb-noun, &lt;300 lines total, HARD GATE present, INDEX row matches.
+3. Write `specs/STOCKTAKE-<date>.md` with findings table (skill, issue, severity).
+4. Critical findings → `plan-work` story; cosmetic → `evolve-skill` candidate.
 
 ## Verify
 

package/CHANGELOG.md

@@ -1,3 +1,10 @@
+## [2.7.4](https://github.com/danielvm-git/bigpowers/compare/v2.7.3...v2.7.4) (2026-06-20)
+
+
+### Bug Fixes
+
+* **skills:** apply e14 changes at source level, fix doctrine checks ([daad805](https://github.com/danielvm-git/bigpowers/commit/daad8054a15d55b433ea1d39b1bd2650ceb9a62a)), closes [hi#fix-rate](https://github.com/hi/issues/fix-rate)
+
 ## [2.7.3](https://github.com/danielvm-git/bigpowers/compare/v2.7.2...v2.7.3) (2026-06-20)
 
 

package/SKILL-INDEX.md

@@ -3,7 +3,7 @@
 > **DO NOT EDIT** — This file is auto-generated by `scripts/generate-skill-index.sh`.
 > Edit `SKILL.md` source files or `skills-lock.json` instead. Run `bash scripts/sync-skills.sh` to regenerate.
 
-**Generated:** 2026-06-20T19:16:20Z
+**Generated:** 2026-06-20T19:29:29Z
 **Skills:** 62
 
 ---

package/commit-message/SKILL.md

@@ -26,7 +26,8 @@ description: Reviews working-tree changes, then drafts a Conventional Commits ti
 3. **Classify for semantic release** — `fix` → patch, `feat` → minor, **breaking** → major.
 4. **Write the message** — `type(optional-scope)!: description` (see [REFERENCE.md](REFERENCE.md#message-format)). Use `!` or a `BREAKING CHANGE:` footer when behavior contracts change.
 5. **Note defensive-code categories touched** — from CONVENTIONS.md: Rate limit | Retry with backoff | Circuit breaker | Timeout | Graceful degradation
-6. **Deliver** — Output:
+6. **Note fix-ratio contribution** — Each `fix:` commit counts toward `metrics.commit_ratio.fix` in `specs/state.yaml`. After `release-branch`, `session-state` recalculates the ratio automatically. A high fix rate (>30%) triggers a deploy + smoke-test suggestion.
+7. **Deliver** — Output:
    - Proposed **full commit message** (title + optional body + footers).
    - **Release bump** this commit would drive: `patch` | `minor` | `major` | `none`.
    - Optional `git add …` and `git commit -m` instructions; do **not** run destructive git commands unless the user asked.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bigpowers",
-  "version": "2.7.3",
+  "version": "2.7.4",
   "description": "61 agent skills for spec-driven, test-first software development by solo developers",
   "main": "index.js",
   "scripts": {

package/release-branch/SKILL.md

@@ -20,11 +20,13 @@ Read `specs/state.yaml` key `workflow_mode` first (`team-pr` | `solo-git`). Fall
 
 | Mode | When | Ship path |
 |------|------|-----------|
-| **solo-local** | `workflow_mode: solo-git` (or `profiles/solo-git.md` present as fallback) | `bash scripts/land-branch.sh <branch> "<conventional message>"` |
+| **solo-local** | `workflow_mode: solo-git` (or `profiles/solo-git.md` present as fallback) | Auto-detect: if `scripts/land-branch.sh` exists → use it; else → fallback (see Step 5) |
 | **team-pr** | `workflow_mode: team-pr` (default) | `gh pr create` → `gh pr merge --squash` |
 
 If unsure and working alone, prefer **solo-local**.
 
+> **Auto-detect note:** The solo-local path first checks if `scripts/land-branch.sh` exists and is executable. If present, the script handles the full squash-merge workflow. If absent, the built-in fallback sequence runs instead.
+
 ## Process
 
 ### 1. Final verification
@@ -50,11 +52,42 @@ Options: **Release (solo-local)** / **Open PR** / **Keep branch** / **Discard**
 
 ### 5. Solo-local integrate
 
-Run `commit-message` to produce the squash commit subject, then:
+Run `commit-message` to produce the squash commit subject. Then auto-detect the integration path:
+
+**Path A — `scripts/land-branch.sh` exists (happy path):**
 ```bash
 bash scripts/land-branch.sh <task-slug> "feat(scope): description"
 ```
 
+**Path B — `scripts/land-branch.sh` missing (fallback):**
+```bash
+# Fallback: manual squash-merge when land-branch.sh is absent
+FEATURE_BRANCH=<task-slug>
+DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo main)
+
+# Ensure we're on the feature branch
+if [ "$(git branch --show-current)" != "$FEATURE_BRANCH" ]; then
+  git checkout "$FEATURE_BRANCH"
+fi
+
+# Checkout default branch and update
+git checkout "$DEFAULT_BRANCH"
+git pull --rebase origin "$DEFAULT_BRANCH" 2>/dev/null || git pull origin "$DEFAULT_BRANCH"
+
+# Squash-merge the feature branch
+git merge --no-ff "$FEATURE_BRANCH" -m "<conventional-commit-message>"
+
+# Push
+git push origin "$DEFAULT_BRANCH"
+
+# Clean up local feature branch
+git branch -d "$FEATURE_BRANCH"
+```
+
+**Report which path was taken.** Print exactly:
+- `"used land-branch.sh"` if Path A
+- `"used fallback merge (land-branch.sh not found)"` if Path B
+
 ### 6. Create PR (team-pr only)
 
 See [REFERENCE.md](REFERENCE.md) for the full PR body template and gh commands.
@@ -95,6 +128,12 @@ git checkout main && git status && pwd
 
 Report: "Branch released. Integrate mode: <solo-local|team-pr>. cwd: $(pwd) on $(git branch --show-current)."
 
+## Solo-local fallback detail
+
+The fallback sequence (Path B above) handles the "remote has moved" case with `git pull --rebase`. Use when `scripts/land-branch.sh` is absent.
+
+**Acceptance:** When fallback runs, main is updated, feature branch is deleted locally, and output states `"used fallback merge (land-branch.sh not found)"`.
+
 ## Handoff
 
 Gate: READY -> next: survey-context

package/session-state/SKILL.md

@@ -70,30 +70,19 @@ Whenever a significant decision is made or a milestone is reached:
 
 ## State Write-Lock Protocol
 
-> **HARD GATE** — Before any write to `specs/state.yaml` or `specs/execution-status.yaml`, acquire `specs/state.yaml.lock`. Release it immediately after the write. A stale lock (>60s) may be force-released.
+> **HARD GATE** — Lock `specs/state.yaml.lock` before writes; stale (>60s) may be force-released.
 
-### Acquire
-
-1. Check if `specs/state.yaml.lock` exists.
-2. If it exists, read the agent ID and timestamp inside.
-3. If the lock is stale (>60s old), remove it and proceed.
-4. If the lock is fresh (<60s), wait 2s and retry (max 15 attempts = 30s).
-5. Write `agent_id: <name>\nacquired_at: <ISO-8601>` to `specs/state.yaml.lock`.
-
-### Release
-
-1. After the write to `state.yaml` or `execution-status.yaml` completes:
-2. `rm specs/state.yaml.lock`
-
-### Lock format (`specs/state.yaml.lock`)
+1. Check lock exists. If fresh (<60s), wait 2s retry (max 15). Stale → remove.
+2. Write `agent_id: <name>\nacquired_at: <ISO-8601>` to lock.
+3. After write, `rm specs/state.yaml.lock`.
 
+Lock format:
 ```yaml
 agent_id: session-state
 acquired_at: "2026-06-11T14:30:00Z"
 ```
 
 
-
 ## Operations
 
 ### show-state (absorbed)
@@ -140,6 +129,16 @@ handoff:
   next_skill: survey-context
 ```
 
+## Tracking commit ratio
+
+After `release-branch` lands, compute fix-to-feature ratio via:
+```bash
+FEAT_COUNT=$(git log main --oneline --grep="^feat" | wc -l | tr -d ' ')
+FIX_COUNT=$(git log main --oneline --grep="^fix" | wc -l | tr -d ' ')
+FIX_PCT=$((FIX_COUNT * 100 / (FEAT_COUNT + FIX_COUNT)))
+```
+Update `specs/state.yaml` `metrics.commit_ratio` with counts. If `fix_pct > 30%`, emit: `"High fix rate (N%) — deploy + smoke-test recommended"`.
+
 ## Anti-Patterns
 
 - **Duplicate Plan**: Don't copy `release-plan.yaml` or epic shards into `state.yaml`.

package/skills-lock.json

@@ -28,7 +28,7 @@
     },
     "commit-message": {
       "description": "Reviews working-tree changes, then drafts a Conventional Commits title/body and states the semantic-release version bump a single such commit would imply. Also notes which defensive-code categories were touched. Use when the user wants to commit recent work, prepare a Conventional Commits message, or asks for semantic-release / semver-consistent messaging before git commit.",
-      "sha256": "c97c86ebffaefb74",
+      "sha256": "aeb104cdbd19b73e",
       "path": "commit-message/SKILL.md"
     },
     "compose-workflow": {
@@ -188,7 +188,7 @@
     },
     "release-branch": {
       "description": "Make the merge/PR/keep/discard decision for a feature branch, verify coverage gates, create the PR with gh, and clean up the worktree. Use when a feature is done and ready to ship, or when user says \"release\", \"merge\", or \"open a PR\".",
-      "sha256": "1668285610d04ff5",
+      "sha256": "70fc37ac4e22143d",
       "path": "release-branch/SKILL.md"
     },
     "request-review": {
@@ -238,7 +238,7 @@
     },
     "session-state": {
       "description": "Track implementation decisions and progress in specs/state.yaml to prevent context rot. Use at the start of a session to load context, and whenever a significant decision is made or a milestone is reached.",
-      "sha256": "68509078a871ee38",
+      "sha256": "5ac473ace06c72b1",
       "path": "session-state/SKILL.md"
     },
     "setup-environment": {
@@ -263,7 +263,7 @@
     },
     "stocktake-skills": {
       "description": "Sequential subagent batch audit of the bigpowers skill catalog — Quick Scan (changed only) or Full (all skills). Use during sustain phase, before a major release, or when catalog drift is suspected.",
-      "sha256": "a164a64360ef29ec",
+      "sha256": "84a4cba67602028f",
       "path": "stocktake-skills/SKILL.md"
     },
     "survey-context": {

package/stocktake-skills/SKILL.md

@@ -15,13 +15,14 @@ Audit SKILL.md catalog for drift, stale triggers, missing HARD GATEs, and INDEX
 | Mode | Scope |
 |------|-------|
 | **Quick Scan** | Skills changed since last tag or in current diff |
-| **Full** | All 58 skills per SKILL-INDEX.md |
+| **Full** | All 62 skills per SKILL-INDEX.md + catalog audit |
 
 ## Process
 
-1. Run mode; for each skill check: exists, verb-noun, <300 lines total, HARD GATE present, INDEX row matches.
-2. Write `specs/STOCKTAKE-<date>.md` with findings table (skill, issue, severity).
-3. Critical findings → `plan-work` story; cosmetic → `evolve-skill` candidate.
+1. Run `bash scripts/audit-catalog.sh` to verify pi/skills ↔ source SKILL.md sync. Mismatch is a critical finding.
+2. Run mode; for each skill check: exists, verb-noun, &lt;300 lines total, HARD GATE present, INDEX row matches.
+3. Write `specs/STOCKTAKE-<date>.md` with findings table (skill, issue, severity).
+4. Critical findings → `plan-work` story; cosmetic → `evolve-skill` candidate.
 
 ## Verify