How this command is triggered — by the user, by Claude, or both
Slash command
/beads:comments issue-idThe summary Claude sees in its command listing — used to decide when to auto-load this command
View or add comments to a beads issue. ## View Comments To view all comments on an issue: - $1: Issue ID (e.g., bd-123) Use the beads CLI `bd comments <issue-id>` to list all comments. Show them to the user with timestamps and authors. ## Add Comment To add a comment: - $1: "add" - $2: Issue ID - $3: Comment text (or use -f flag for file input) Use `bd comments add <issue-id> "comment text"` to add a comment. Confirm the comment was added successfully. Comments are useful for: - Progress updates during work - Design notes or technical decisions - Links to related resources - Question...
View or add comments to a beads issue.
To view all comments on an issue:
Use the beads CLI bd comments <issue-id> to list all comments. Show them to the user with timestamps and authors.
To add a comment:
Use bd comments add <issue-id> "comment text" to add a comment. Confirm the comment was added successfully.
Comments are useful for:
npx claudepluginhub cpdata/beads/commentsViews or adds comments on a beads issue using the beads CLI. Supports a threaded discussion workflow separate from issue metadata editing.
/commentsRemoves obvious and redundant comments from uncommitted git changes. Keeps TODOs, linter directives, and empty block notes; moves end-of-line comments above code.