بنقرة واحدة
kb-close
Complete a task with verification — check acceptance criteria, require evidence, update status
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Complete a task with verification — check acceptance criteria, require evidence, update status
التثبيت باستخدام 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
Commit workspace changes to the knowledge base with validation
Load and validate project context, bootstrapping if needed
| name | kb-close |
| description | Complete a task with verification — check acceptance criteria, require evidence, update status |
Close a task after verifying all acceptance criteria are met. This enforces AGENTS.md rule #8: "Complete document body before status updates."
Input: $ARGUMENTS
The argument should be a task slug (e.g. tasks/my-task).
Use kb_show to load the task document. If not found, show available tasks and ask.
Parse the document body for acceptance criteria (lines matching - [ ] or - [x]).
Count and report:
[x]) — completed[ ]) — remainingIf unchecked items remain, show each one and ask the user:
"These acceptance criteria are not yet checked:
- Criterion A
- Criterion B
Are these actually done (I'll check them off), no longer relevant (I'll remove them), or still outstanding (we should not close yet)?"
Do NOT proceed to close if the user says items are still outstanding.
Check if the document has a "Completion Evidence" section (commit hashes, PR links, test results, verification steps). This is distinct from the "Progress Log" (chronological work entries). Both are valuable, but completion evidence is the proof that the work was actually done.
If neither section exists, warn:
"This task has no completion evidence. Before closing, consider adding:
- Commit hashes or PR links
- Test results
- Verification steps taken"
Offer to add a "Completion Evidence" section based on what's known.
Use kb_graph to see if this task has children or blocks other tasks:
kb_unlink (e.g. kb_unlink with child: "<child-slug>", container: "<this-slug>"). Continue anyway?"
Checkout the task and update it:
### YYYY-MM-DD\n- Task completed. [summary]"Complete task: <title>"Only after the body is updated and committed:
kb_set with slug: "<task-slug>", status: "completed"
Show: