prizmkit 1.0.45 → 1.0.58

package/bundled/skills/prizm-kit/assets/codebuddy-md-template.md

@@ -1,35 +0,0 @@
-## PrizmKit Documentation Framework
-
-This project uses PrizmKit with the Prizm documentation system for AI-optimized progressive context loading.
-
-### Progressive Loading Protocol
-- ON SESSION START: Always read `.prizm-docs/root.prizm` first (L0 — project map)
-- ON TASK: Read L1 (`.prizm-docs/<module>.prizm`) for relevant modules referenced in MODULE_INDEX
-- ON FILE EDIT: Read L2 (`.prizm-docs/<module>/<submodule>.prizm`) before modifying files. Pay attention to TRAPS and DECISIONS.
-- NEVER load all .prizm docs at once. Load only what is needed for the current task.
-
-### Auto-Update Protocol
-- BEFORE EVERY COMMIT: Update affected `.prizm-docs/` files
-- The UserPromptSubmit hook will remind you automatically
-- Use `prizmkit-committer` skill for the complete commit workflow
-
-### Doc Format Rules
-- All `.prizm` files use KEY: value format, not prose
-- Size limits: L0 = 4KB, L1 = 3KB, L2 = 5KB
-- Arrow notation (->) indicates load pointers to other .prizm docs
-- DECISIONS and CHANGELOG are append-only (never delete entries)
-
-### Creating New L2 Docs
-- When you first modify files in a sub-module that has no L2 doc:
-  1. Read the source files in that sub-module
-  2. Generate a new L2 `.prizm` file following Prizm specification
-  3. Add a pointer in the parent L1 doc's SUBDIRS section
-
-### Fast Path for Simple Changes
-Not every change needs the full spec -> plan -> tasks workflow. Use fast path for:
-- Bug fixes with clear root cause, config tweaks, typo fixes, simple refactors
-- Documentation-only changes, test additions for existing code
-- Directly use `prizmkit.implement` with inline task description, then `prizmkit.commit`
-
-Use the full workflow (specify -> plan -> tasks -> analyze -> implement) for:
-- New features, multi-file coordinated changes, architectural decisions, data model or API changes

package/bundled/skills/prizm-kit/assets/hooks/prizm-commit-hook.json

@@ -1,15 +0,0 @@
-{
-  "hooks": {
-    "UserPromptSubmit": [
-      {
-        "matcher": "\\b(commit|Commit|push|Push|finish|Finish|ship|Ship|merge|Merge|pull request|Pull Request|pr|PR)\\b|提交|推送|收尾|完成任务|合并|发版|发布",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "echo 'PRIZMKIT_DOC_UPDATE_REQUIRED: Before committing, you MUST update .prizm-docs/ per Prizm auto-update protocol. Steps: 1) Run git diff --cached --name-status. 2) Map changed files to modules via root.prizm MODULE_INDEX. 3) Read and update affected .prizm files (only changed sections). 4) Append to changelog.prizm. 5) Stage .prizm files with git add .prizm-docs/. 6) Then proceed with commit using prizmkit-committer workflow. RULES: Never rewrite entire .prizm files. Never add prose. Only update affected sections.'"
-          }
-        ]
-      }
-    ]
-  }
-}

package/bundled/skills/prizmkit-summarize/SKILL.md

@@ -1,51 +0,0 @@
----
-name: "prizmkit-summarize"
-description: "Archive completed features to REGISTRY.md. Extracts metadata from specs, scans code, updates feature index. Invoke after code review passes or feature is done. (project)"
----
-
-# PrizmKit Summarize
-
-Archive completed features to the feature registry. Extracts metadata from specs and code, generates a registry entry, and appends a changelog record. Idempotent — re-running produces the same output.
-
-## Commands
-
-### prizmkit.summarize
-
-Archive a completed feature to the registry.
-
-**PRECONDITION:** `spec.md`, `plan.md`, `tasks.md` exist in `.prizmkit/specs/###-feature-name/`
-
-**STEPS:**
-
-1. Read `spec.md`, `plan.md`, `tasks.md`
-2. Analyze `tasks.md` completion rate — warn if < 100%
-3. Scan actual code directories for core file paths
-4. Generate REGISTRY entry:
-   - Feature number and name
-   - Branch name
-   - Status (complete/partial)
-   - Key files and directories
-   - API endpoints added/modified
-   - Data model changes
-   - Completion date
-5. Append to `.prizmkit/specs/REGISTRY.md` (create from template `${SKILL_DIR}/assets/registry-template.md` if not exists)
-6. Append changelog entry
-7. Output: registry entry summary
-
-**KEY RULES:**
-- Idempotent: same input MUST produce same output on re-run
-- If `tasks.md` completion < 100%, status is "Partial" with warning
-- REGISTRY.md is append-only — never modify existing entries
-- Changelog entries use format: `YYYY-MM-DD | [###] [Feature Name] | [Status]`
-- If REGISTRY.md does not exist, create it from template before appending
-- **Bug fixes MUST NOT create new REGISTRY.md entries.** Bugs are refinements of incomplete existing features, not new functionality. Bug fix commits should only update the original feature's changelog, not generate a new registry entry. Do NOT invoke this skill for bug fix commits.
-
-**HANDOFF:** `prizmkit.specify` (start next feature) or `prizmkit.retrospective` (extract lessons)
-
-## Template
-
-The registry template is located at `${SKILL_DIR}/assets/registry-template.md`.
-
-## Output
-
-- `.prizmkit/specs/REGISTRY.md` — Updated with new feature entry and changelog record

package/bundled/skills/prizmkit-summarize/assets/registry-template.md

@@ -1,18 +0,0 @@
-# PrizmKit Feature Registry
-
-> Auto-generated by prizmkit-summarize. Do not edit manually.
-
-## Features
-
-### [###] [Feature Name]
-- **Branch**: ###-feature-name
-- **Status**: Complete | Partial
-- **Date**: YYYY-MM-DD
-- **Key Files**: [list]
-- **API Changes**: [summary]
-- **Data Changes**: [summary]
-
----
-
-## Changelog
-- YYYY-MM-DD | [###] [Feature Name] | [Status]

package/bundled/templates/hooks/commit-intent-claude.json

@@ -1,26 +0,0 @@
-{
-  "hooks": {
-    "UserPromptSubmit": [
-      {
-        "matcher": "\\b(commit|Commit|push|Push|finish|Finish|ship|Ship|merge|Merge|pull request|Pull Request|pr|PR)\\b|提交|推送|收尾|完成任务|合并|发版|发布",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "SRC=$(git diff --cached --name-only 2>/dev/null | grep -cE '\\.(ts|tsx|js|jsx|py|go|rs|java)$'); if [ \"$SRC\" -gt 0 ]; then PRIZM=$(git diff --cached --name-only 2>/dev/null | grep -c '^\\.prizm-docs/'); if [ \"$PRIZM\" -gt 0 ]; then echo \"PRIZMKIT_DOC_STATUS: $SRC source file(s) staged | .prizm-docs/ updated ($PRIZM file(s))\"; else echo \"PRIZMKIT_DOC_STATUS: $SRC source file(s) staged | .prizm-docs/ NOT UPDATED — update if this is a feature change\"; fi; fi"
-          }
-        ]
-      }
-    ],
-    "PostToolUse": [
-      {
-        "matcher": "Bash",
-        "hooks": [
-          {
-            "type": "command",
-            "command": "if echo \"$CLAUDE_TOOL_INPUT\" 2>/dev/null | grep -qE 'git (commit|merge|rebase)' 2>/dev/null; then DRIFT=$(sh .prizmkit/scripts/diff-prizm-docs.sh 2>/dev/null); if [ -n \"$DRIFT\" ]; then echo \"PRIZMKIT_DRIFT_DETECTED: prizm-docs structural differences found after git operation:\"; echo \"$DRIFT\"; echo \"Please update affected .prizm-docs/ files using /prizmkit-prizm-docs.\"; fi; fi"
-          }
-        ]
-      }
-    ]
-  }
-}