菜单
Write agent_logs entries correctly in KanbAgent. Activates when an agent needs to log an action, when completing a task, starting a session, or when agent_logs entries are missing. Triggers on "log this", "insert agent_log", "add a log", or any task_started/task_done/session_end event.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Start an agent session correctly in KanbAgent. Activates when an agent needs to begin work, when user says "start a session", "launch agent X", "begin session", or when an agent role is invoked and no active session exists. Ensures correct startup sequence: dbstart → read tasks → begin work.
Write an Architecture Decision Record (ADR) for KanbAgent following the project's existing format. Activates when a structural decision needs to be documented, when agent arch completes a design decision, or when user says "ADR", "architecture decision", "document this choice".
Create a new typed IPC handler in KanbAgent following the full stack pattern. Activates when user or agent needs to add a new IPC channel, expose a new API to the renderer, or wire a new feature across main/preload/renderer. Triggers on "add IPC", "new handler", "expose to renderer", "new IPC channel", "create a handler".
Create a versioned SQLite migration for KanbAgent. Activates when the DB schema needs to change, when user says "add a column", "create a table", "migration", "alter schema", "add a column", "modify the schema". Follows the existing migration pattern with idempotency and better-sqlite3 compatibility.
Execute a release in KanbAgent following the full devops + review protocol. Activates when agent devops receives a release ticket, when user says "release", "publish version", "bump version", "npm run release". Covers prerequisites, version bump, CI wait, GitHub Release publication.
Complete a task ticket in KanbAgent following the mandatory order. Activates when an agent finishes work on a task, when user says "mark as done", "ticket done", "close ticket", "close task". Enforces comment-first then done order, session closure, and backlog check.
| name | agent-log-writing |
| description | Write agent_logs entries correctly in KanbAgent. Activates when an agent needs to log an action, when completing a task, starting a session, or when agent_logs entries are missing. Triggers on "log this", "insert agent_log", "add a log", or any task_started/task_done/session_end event. |
Correct insertion of agent_logs entries for KanbAgent. Mandatory at minimum for 2 events per task.
| Event | When | level |
|---|---|---|
task_started | Right after UPDATE tasks SET status='in_progress' | info |
task_done | Right before UPDATE tasks SET status='done' | info |
session_start | In agent-session-starting Step 1b (all agents) | info |
| Event | When | level |
|---|---|---|
session_start | review/devops: start of session | info |
task_archived | review: after archiving a ticket | info |
task_rejected | review: after rejecting a ticket | warn |
task_created | review/task-creator: after creating a ticket | info |
session_end | review/devops: just before closing session | info |
INSERT INTO agent_logs (session_id, agent_id, level, action, detail, created_at) VALUES (<session_id>, <agent_id>, '', '', '', CURRENT_TIMESTAMP);
-- task_started INSERT INTO agent_logs (session_id, agent_id, level, action, detail, created_at) VALUES (42, 3, 'info', 'task_started', 'T912: feat(ipc): add agent-groups handler', CURRENT_TIMESTAMP);
-- task_done INSERT INTO agent_logs (session_id, agent_id, level, action, detail, created_at) VALUES (42, 3, 'info', 'task_done', 'T912: feat(ipc): add agent-groups handler', CURRENT_TIMESTAMP);
-- review: task_archived INSERT INTO agent_logs (session_id, agent_id, level, action, detail, created_at) VALUES (55, 4, 'info', 'task_archived', 'T912 archived: implementation correct', CURRENT_TIMESTAMP);
-- review: task_rejected INSERT INTO agent_logs (session_id, agent_id, level, action, detail, created_at) VALUES (55, 4, 'warn', 'task_rejected', 'T912 rejected: missing input validation in handler', CURRENT_TIMESTAMP);
-- review: session_end INSERT INTO agent_logs (session_id, agent_id, level, action, detail, created_at) VALUES (55, 4, 'info', 'session_end', 'Session done. Archived:2 Rejected:1', CURRENT_TIMESTAMP);
When chaining multiple tasks in one session without /clear:
-- End of task 1 INSERT INTO agent_logs (...) VALUES (, , 'info', 'task_done', 'T910: ...', CURRENT_TIMESTAMP); UPDATE tasks SET status='done' ... WHERE id=910;
-- Start of task 2 (immediately after) INSERT INTO agent_logs (...) VALUES (, , 'info', 'task_started', 'T911: ...', CURRENT_TIMESTAMP); UPDATE tasks SET status='in_progress' ... WHERE id=911;
Same session_id throughout, only task_id changes.
