Menu
Add a comment to an issue.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Document a completed issue in the wiki (functional, technical, decision, solution).
Summarize a ticket's history, description, comments, and status.
Summarize recent activity across issues and commits.
Start tracked work: find/create ticket, set in-progress, track progress in comments.
Bump the tracker VERSION (semver) so update-check hook notifies existing installs.
Create a new issue (ticket, bug, feature request).
| name | add-comment |
| description | Add a comment to an issue. |
| argument-hint | <ISSUE-ID> <comment> |
| allowed-tools | Read, Write, Glob |
Add a comment to an existing issue.
content)Keep comments short. Future sessions re-read these — every word costs tokens.
path:line format only when load-bearing..project/issues/$1/issue.json to verify it exists.project/issues/$1/comments/ if it doesn't exist{number}.json with ALL of these fields (all required):
id: zero-padded comment number (e.g. "001")author: "Claude Code"content: $ARGUMENTS (everything after the issue ID)created: current ISO-8601 timestamp — REQUIRED, omitting this breaks the issue APIissue.json updated timestamp.project/issues_index.json (create as [] if missing). Replace the entry with matching id (or add if missing) using all fields from issue.json. Sort by updated descending. Write back.