菜单
Commit workspace changes to the knowledge base with validation
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use GitKB code intelligence tools instead of grep for finding callers, definitions, usages, and dead code. Trigger when exploring code relationships or searching for symbol usage.
Explore codebase with code intelligence and search across code and documents. Use when searching by concept, finding where functionality lives, or investigating unfamiliar code.
Manage GitKB knowledge base for project documentation, tasks, and context. Use when working with KB documents, viewing tasks, updating progress, or managing project knowledge.
Show GitKB kanban board with task status columns
Complete a task with verification — check acceptance criteria, require evidence, update status
Load and validate project context, bootstrapping if needed
| name | kb-commit |
| description | Commit workspace changes to the knowledge base with validation |
Review, validate, and commit pending workspace changes.
Use kb_status to see what will be committed, then kb_diff to review actual changes.
Check for common issues in the diff:
Status change without body update (AGENTS.md rule #8):
If a document's status field changed to completed/done/resolved but the body has no corresponding updates (no completion evidence, no checked acceptance criteria), warn the user:
"This changes status to completed but the document body doesn't show completion evidence. Consider adding a Completion Evidence section or checking off acceptance criteria before committing."
Graph-derived fields being committed:
If the diff shows changes to fields that are graph-derived (blocks, children, references), warn:
"The field
blocksis graph-derived — it's computed from other documents'blocked_byfields. Committing it may cause unexpected behavior. Consider removing it from the frontmatter."
Empty or skeleton documents: If a new document has only frontmatter and no body content, warn:
"This document has no body content. Consider adding at least an Overview section before committing."
Analyze the changes and draft a concise commit message:
From the kb_status output, identify which documents you modified in this session. Only commit those documents — never commit the entire workspace blindly.
Use kb_commit with:
message: the generated commit messagepathspecs: array of slugs you modified (e.g. ["tasks/my-task", "incidents/inc-007"])If kb_status shows documents you didn't modify, exclude them from pathspecs. Those are likely another agent's uncommitted work. Warn the user:
"kb_status shows changes to
<slug>which I didn't modify. Excluding it from this commit. Another agent may have pending changes."
Show what was committed and the resulting state.