PrizmKit Committer

Automated commit workflow that keeps Prizm documentation in sync, manages changelog entries, and captures learnings from each commit.

When to Use

• User says "commit", "提交", "finish", "done with this task", "ship it"
• After implementing a feature or fixing a bug
• The UserPromptSubmit hook will remind to use this skill

Workflow

Follow these steps STRICTLY in order:

Step 1: Status Check

git status

• If "nothing to commit, working tree clean": inform user and stop
• If there are changes: proceed

Step 2: Prizm Documentation Update (CRITICAL — must complete before commit)

2a. Get changed files:

git diff --cached --name-status

If nothing staged, also check:

git diff --name-status

2b. Read .prizm-docs/root.prizm to get MODULE_INDEX

2c. Map each changed file to its module using MODULE_INDEX paths

2d. For each affected module:

• IF L2 doc exists (.prizm-docs/<module>/<submodule>.prizm):
  • Update KEY_FILES (add new files, remove deleted, note modified)
  • Update INTERFACES (if public signatures changed)
  • Update DEPENDENCIES (if imports changed)
  • Append to module CHANGELOG section
  • Update UPDATED timestamp
• IF L1 doc exists (.prizm-docs/<module>.prizm):
  • Update FILES count
  • Update KEY_FILES (if major files added/removed)
  • Update UPDATED timestamp
• Update root.prizm:
  • Update MODULE_INDEX file counts (only if counts changed)
  • UPDATED timestamp (only if structural changes)

2e. Append to .prizm-docs/changelog.prizm: Format: - YYYY-MM-DD | <module-path> | <verb>: <one-line description> Verbs: add, update, fix, remove, refactor, rename, deprecate

2f. Stage prizm docs:

git add .prizm-docs/

SKIP CONDITIONS for doc update:

• Only internal implementation changed (no interface/dependency change)
• Only comments, whitespace, or formatting changed
• Only test files changed
• Only .prizm files changed (avoid circular updates)

Step 3: Diff Analysis

git diff HEAD

Analyze:

• Type: feat, fix, refactor, docs, test, chore, perf, style, ci, build
• Scope: affected module name
• Description: imperative mood summary

Step 4: Update CHANGELOG.md

If CHANGELOG.md exists, append entry following Keep a Changelog format. If manage_changelog.py exists in skill scripts:

python3 ${SKILL_DIR}/scripts/manage_changelog.py add --type <type> --message "<description>"

Step 5: Git Commit

git add .
git commit -m "<type>(<scope>): <description>"

Follow Conventional Commits format.

Step 6: Verification

git log -1 --stat

Step 7: Optional Push

Ask user: "Push to remote?"

• Yes: git push
• No: Stop

Error Handling

• If git diff is empty but untracked files exist: run git add -N . first
• If CHANGELOG.md script fails: update manually or ask user
• If .prizm-docs/ doesn't exist: skip Step 2 entirely (project not initialized)