append_issue_log
Add progress updates, notes, or activity records to an issue's audit trail for tracking work history and maintaining transparency in task execution.
Instructions
Appends content to an issue's log in the task trellis system
Use this tool to add progress updates, notes, or activity records to an issue's audit trail. Essential for tracking work history, documenting decisions, and maintaining transparency in task execution.
Log entry purposes:
Record progress milestones and status changes
Document challenges encountered and solutions applied
Note important decisions or changes in approach
Track time spent or resources used
Log external dependencies or blockers
Record completion details and outcomes
Log content guidelines:
Use clear, descriptive entries with context
Include timestamps (automatically added by system)
Reference specific files, commits, or external resources when relevant
Note any changes to scope, requirements, or approach
Document lessons learned or insights gained
Activity tracking patterns:
Starting work: "Started implementation of feature X"
Progress updates: "Completed database schema changes, moving to API layer"
Blocking issues: "Blocked on external API access, contacted team"
Problem resolution: "Resolved memory leak by optimizing data structure"
Completion: "Task completed, all tests passing, PR submitted"
The log creates a permanent audit trail that helps with project retrospectives, debugging issues, and understanding work evolution over time.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ID of the issue to append log to | |
| contents | Yes | Contents to append to the log |
Implementation Reference
- src/tools/appendObjectLogTool.ts:49-60 (handler)The async handler function `handleAppendObjectLog` that executes the core tool logic by extracting id and contents from args and calling `service.appendObjectLog(repository, id, contents)`. This is the main implementation of the tool.export async function handleAppendObjectLog( service: TaskTrellisService, repository: Repository, args: unknown, ) { const { id, contents } = args as { id: string; contents: string; }; return service.appendObjectLog(repository, id, contents); }
- The tool definition object `appendObjectLogTool` containing the name, detailed description, and inputSchema specifying required 'id' (string) and 'contents' (string) parameters.export const appendObjectLogTool = { name: "append_issue_log", description: `Appends content to an issue's log in the task trellis system Use this tool to add progress updates, notes, or activity records to an issue's audit trail. Essential for tracking work history, documenting decisions, and maintaining transparency in task execution. Log entry purposes: - Record progress milestones and status changes - Document challenges encountered and solutions applied - Note important decisions or changes in approach - Track time spent or resources used - Log external dependencies or blockers - Record completion details and outcomes Log content guidelines: - Use clear, descriptive entries with context - Include timestamps (automatically added by system) - Reference specific files, commits, or external resources when relevant - Note any changes to scope, requirements, or approach - Document lessons learned or insights gained Activity tracking patterns: - Starting work: "Started implementation of feature X" - Progress updates: "Completed database schema changes, moving to API layer" - Blocking issues: "Blocked on external API access, contacted team" - Problem resolution: "Resolved memory leak by optimizing data structure" - Completion: "Task completed, all tests passing, PR submitted" The log creates a permanent audit trail that helps with project retrospectives, debugging issues, and understanding work evolution over time.`, inputSchema: { type: "object", properties: { id: { type: "string", description: "ID of the issue to append log to", }, contents: { type: "string", description: "Contents to append to the log", }, }, required: ["id", "contents"], }, } as const;
- src/server.ts:266-267 (registration)Registration in the tool dispatch switch statement in `CallToolRequestSchema` handler, mapping the tool name to its handler function.case "append_issue_log": return handleAppendObjectLog(_getService(), repository, args);
- src/server.ts:183-183 (registration)The tool is included in the array returned by the `ListToolsRequestSchema` handler for tool discovery.appendObjectLogTool,