prizmkit 1.1.36 → 1.1.37

package/bundled/VERSION.json

@@ -1,5 +1,5 @@
 {
-  "frameworkVersion": "1.1.36",
-  "bundledAt": "2026-04-18T05:19:19.256Z",
-  "bundledFrom": "bee43f6"
+  "frameworkVersion": "1.1.37",
+  "bundledAt": "2026-04-19T13:06:01.957Z",
+  "bundledFrom": "b5a91ed"
 }

package/bundled/skills/_metadata.json

@@ -1,5 +1,5 @@
 {
-  "version": "1.1.36",
+  "version": "1.1.37",
   "skills": {
     "prizm-kit": {
       "description": "Full-lifecycle dev toolkit. Covers spec-driven development, Prizm context docs, code quality, debugging, deployment, and knowledge management.",

package/bundled/skills/bug-fix-workflow/SKILL.md

@@ -48,11 +48,12 @@ For trivial bugs with clear root cause and minimal scope:
 1. Branch Setup → `fix/<BUG_ID>-<short-desc>`
 2. Write reproduction test → confirm failing
 3. Apply fix → confirm test passes + full suite green
-4. Ask user: "Quick fix applied. Verify before commit? (Y/skip)"
-5. Commit with `fix(<scope>):` prefix
-6. Ask merge preference
+4. Run `/prizmkit-code-review` for quality check
+5. Ask user: "Quick fix applied. Verify before commit? (Y/skip)"
+6. Commit with `fix(<scope>):` prefix
+7. Ask merge preference
 
-**Fast Path still requires**: fix branch, reproduction test, full test suite pass, user merge decision.
+**Fast Path still requires**: fix branch, reproduction test, full test suite pass, code review, user merge decision.
 
 ---
 
@@ -196,9 +197,11 @@ AskUserQuestion:
 ```
 
 - **Plan and fix now** → Invoke `/prizmkit-plan` with `artifact_dir=.prizmkit/bugfix/<BUG_ID>/`:
-  1. prizmkit-plan generates `spec.md` + `plan.md` under `.prizmkit/bugfix/<BUG_ID>/`
-  2. Invoke `/prizmkit-implement` to execute the plan
-  3. After implementation, resume this workflow at Phase 5 (Review)
+  1. `/prizmkit-plan` generates `spec.md` (bug description + acceptance criteria) + `plan.md` (fix strategy + test specifications) under `.prizmkit/bugfix/<BUG_ID>/`
+  2. Invoke `/prizmkit-implement` to execute the plan (TDD: write failing reproduction test → implement fix → tests pass)
+  3. Run `/prizmkit-code-review` for quality check
+  4. Commit via `/prizmkit-committer` with `fix(<scope>):` prefix
+  5. **End workflow** — skip Phase 2-7. No `/prizmkit-retrospective` (bug fixes are incomplete features, not new architecture)
 - **Add to bug-fix-list.json** → Invoke `bug-planner` to add this bug to `.prizmkit/plans/bug-fix-list.json`, then suggest user run `bugfix-pipeline-launcher` to start the pipeline. End this workflow.
 
 **NEVER proceed with direct code changes without explicit user confirmation via `AskUserQuestion`. Do NOT render options as plain text — the user must be able to click/select.**
@@ -276,22 +279,12 @@ If the fix causes test regressions:
 
 **Goal**: Verify fix quality before committing.
 
-1. **Self-review** the changes:
-   - Does the fix address the root cause (not just the symptom)?
-   - Are there edge cases not covered?
-   - Is the reproduction test thorough enough?
-   - Does the fix follow project conventions?
-2. **Run full test suite** one final time
-3. **Present review summary**:
-   ```
-   Fix Review:
-   - Root cause addressed: Yes (null check added at auth service level)
-   - Edge cases: Covered (401, 403, network error)
-   - Regression: None (48/48 tests pass)
-   - Code quality: Clean, follows existing patterns
-
-   Ready to commit.
-   ```
+1. **Run `/prizmkit-code-review`** to review the fix:
+   - Reviews git diff against the bug context (root cause, fix approach, affected areas)
+   - Iterative Reviewer Agent + Dev Agent loop (max 3 rounds)
+   - Checks: root cause addressed (not just symptom), edge cases covered, reproduction test thoroughness, project conventions
+2. **If PASS**: Proceed to Phase 6
+3. **If NEEDS_FIXES after max rounds**: Present unresolved findings to user, ask whether to proceed or revise
 
 **CHECKPOINT CP-BFW-5**: Code review completed and quality verified.
 
@@ -323,11 +316,8 @@ If user reports the fix is NOT working:
    - Commit message: `fix(<scope>): <description>`
    - Include both fix code and reproduction test
    - Do NOT push (user decides when to push)
-   - **Bug Fix Documentation Policy**:
-     - DEFAULT: Run `/prizmkit-retrospective` with structural sync only (update file counts, interfaces, dependencies). Skip knowledge injection.
-     - UPDATE DOCS when bug fix causes: interface signature changes, dependency additions/removals, observable behavior changes to existing features, or newly discovered TRAPs (gotchas/pitfalls)
-     - When any of the above apply, run full `/prizmkit-retrospective` (Job 1 + Job 2)
    - `/prizmkit-committer` is a pure commit tool — it does NOT modify `.prizm-docs/` or any project files
+   - No `/prizmkit-retrospective` — bug fixes are incomplete features, not new architecture worth documenting
 2. **Ask merge preference**:
    ```
    Fix committed on branch `fix/<BUG_ID>-<short-desc>`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.1.36",
+  "version": "1.1.37",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {