Menú
Add a progress log entry to a task — quick datestamped note and commit
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | kb-progress |
| description | Add a progress log entry to a task — quick datestamped note and commit |
Quickly log progress on a task. This is the most common mid-work operation — add a datestamped note without a full edit cycle.
Input: $ARGUMENTS
Format: <task-slug> <progress note>
Examples:
/kb-progress tasks/my-task Implemented warning system for graph-derived fields. 3 of 5 acceptance criteria done./kb-progress tasks/my-project-28 Created slash command, testing auto-increment logic/kb-progress Fixed the serialization bug, all tests passing now (uses most recently active task)Extract the task slug (first word if it contains /) and progress note (remainder).
If no slug is provided, find the most recently modified active task:
kb_list with type: "task", status: "active"/kb-start."Use kb_show to load the task, then kb_checkout to materialize it.
Read the workspace file. Find or create the ## Progress Log section.
Append a new dated entry at the top of the progress log (reverse chronological):
### YYYY-MM-DD
- [progress note from user]
If a ### YYYY-MM-DD header for today already exists, append the bullet under it instead of creating a new header.
Use the Edit tool to insert the entry. Do not overwrite the file.
If the progress note mentions completing specific acceptance criteria, check them off ([ ] → [x]) in the document body.
Use kb_commit with:
message: "Progress: <short summary>"pathspecs: ["<task-slug>"] (the single document modified in this session)Show:
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
Commit workspace changes to the knowledge base with validation