prizmkit 1.0.1 → 1.0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,5 +1,5 @@
1
1
  {
2
2
  "frameworkVersion": "1.0.0",
3
- "bundledAt": "2026-03-09T15:24:07.558Z",
3
+ "bundledAt": "2026-03-10T01:40:43.750Z",
4
4
  "bundledFrom": "/Users/loneyu/SelfProjects/PrizmKitEvolvingProgramming"
5
5
  }
@@ -31,11 +31,11 @@ export async function generateSettings(targetRoot, options = {}) {
31
31
  if (!existing.hooks.UserPromptSubmit) {
32
32
  existing.hooks.UserPromptSubmit = [
33
33
  {
34
- matcher: '',
34
+ matcher: '(?i)\\b(commit|push|finish|ship|merge|pull request|pr)\\b|提交|推送|收尾|完成任务|合并|发版|发布',
35
35
  hooks: [
36
36
  {
37
37
  type: 'prompt',
38
- prompt: 'If this message mentions committing, pushing, or finishing a task, remind about updating .prizm-docs/ first. Suggest using the prizmkit-committer skill.',
38
+ prompt: 'You are a commit-intent detector for PrizmKit. Analyze the user prompt and determine if the user intends to COMMIT, PUSH, FINISH, SHIP, MERGE, or create a PULL REQUEST.\n\nUser prompt: $ARGUMENTS\n\nIF commit intent detected, respond with:\n{"ok": true, "reason": "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."}\n\nIF no commit intent, respond with:\n{"ok": true}\n\nRespond with JSON only. No explanation.',
39
39
  },
40
40
  ],
41
41
  },
@@ -2,6 +2,7 @@
2
2
  "hooks": {
3
3
  "UserPromptSubmit": [
4
4
  {
5
+ "matcher": "(?i)\\b(commit|push|finish|ship|merge|pull request|pr)\\b|提交|推送|收尾|完成任务|合并|发版|发布",
5
6
  "hooks": [
6
7
  {
7
8
  "type": "prompt",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "prizmkit",
3
- "version": "1.0.1",
3
+ "version": "1.0.3",
4
4
  "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
5
5
  "type": "module",
6
6
  "bin": {
package/src/scaffold.js CHANGED
@@ -335,11 +335,11 @@ async function installSettings(platform, projectRoot, options, dryRun) {
335
335
  hooks: {
336
336
  UserPromptSubmit: [
337
337
  {
338
- matcher: '',
338
+ matcher: '(?i)\\b(commit|push|finish|ship|merge|pull request|pr)\\b|提交|推送|收尾|完成任务|合并|发版|发布',
339
339
  hooks: [
340
340
  {
341
341
  type: 'prompt',
342
- prompt: 'If this message mentions committing, pushing, or finishing a task, remind about updating .prizm-docs/ first. Suggest using the prizmkit-committer skill.',
342
+ prompt: 'You are a commit-intent detector for PrizmKit. Analyze the user prompt and determine if the user intends to COMMIT, PUSH, FINISH, SHIP, MERGE, or create a PULL REQUEST.\n\nUser prompt: $ARGUMENTS\n\nIF commit intent detected, respond with:\n{"ok": true, "reason": "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."}\n\nIF no commit intent, respond with:\n{"ok": true}\n\nRespond with JSON only. No explanation.',
343
343
  },
344
344
  ],
345
345
  },