comment

Posts comments to external ticket backends from wiki task pages via a confirm-token CLI workflow.

2|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill comment-brandtam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: comment
Source: https://github.com/brandtam/rubber-ducky-legacy/tree/main/src/skills/comment
Command: npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill comment-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It lets you add a comment to an external ticket (GitHub, Jira, or Asana) directly from a wiki task page, without leaving your vault or manually switching to the ticket tracker. ## Core Features & Use Cases - Backend detection: Reads the task page's gh_ref, jira_ref, or asana_ref to determine which external system to target. - Confirmed external writes: Uses a risk_class: hard confirm-token flow so no comment is posted without explicit user approval. - Audit trail: The CLI increments comment_count, bumps updated, and appends an audit-log line, while the skill appends the comment body to the page's ## Comments section. - Use Case: You are reviewing a task page for a login bug fix and want to post a status update to the linked Jira ticket without opening Jira. ## Quick Start Ask the agent to add a comment to a task page, for example: comment on wiki/tasks/fix-login-bug.md saying "Great progress on this".

Frequently Asked Questions about comment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add a comment to a Jira or GitHub ticket from a wiki page?▼

Run the comment skill with the task page path and optional comment text. The skill reads the page's backend reference (gh_ref, jira_ref, or asana_ref), requests a confirm-token, and posts the comment via the rubber-ducky CLI.

What happens if the task page has no backend reference?▼

The skill stops and tells you the task has no backend reference. You must first push the task to an external tracker with the /push skill before commenting.

Why does the comment skill require a confirm-token?▼

The skill is classified as risk_class hard because it writes to an external system. The confirm-token ensures the user explicitly approves the action, and the CLI rejects missing, expired, or mismatched tokens before any external call.

Does the CLI update the wiki page after posting a comment?▼

The CLI increments comment_count, bumps the updated timestamp, and appends an audit-log line. The skill then separately appends the formatted comment body to the page's Comments section using the Edit tool.

Can I retry a failed comment with the same token?▼

No. If the comment verb exits non-zero, the token is consumed or invalid. You must request a fresh confirm-token before retrying the comment.