comment

Post comments to external tickets via rubber-ducky CLI using wiki backend references.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/brandtam/rubber-ducky --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/tree/main/src/skills/comment
Command: npx skills add https://github.com/brandtam/rubber-ducky --skill comment-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually posting comments to external tickets from wiki pages is error prone and slow; this skill automates the process, ensuring comments reach the correct backend ticket with an auditable trail.

Core Features & Use Cases

  • Post a comment to an external ticket referenced by a wiki page.
  • Validate and extract the backend reference (gh_ref, jira_ref, or asana_ref) before posting.
  • Use a confirm-token flow to securely publish the comment and update the audit log.

Quick Start

Describe a wiki task page and optional comment text, and have rubber-ducky post the comment to the linked external ticket.

Frequently Asked Questions about comment

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

FAQPage Schema
How do I post a wiki comment to an external ticket automatically?

To post a wiki comment to an external ticket automatically, this skill reads the wiki page, resolves backend references like gh_ref or jira_ref, and uses a confirm-token to securely publish via the rubber-ducky CLI while updating the audit log.

What is a confirm-token and why do I need it to post external ticket comments?

A confirm-token is a required security credential for posting external ticket comments. It ensures authorized publishing through the rubber-ducky CLI, preventing unauthorized submissions and maintaining a secure audit trail.

Can I use this skill to post comments to Jira, Asana, and GitHub tickets?

Yes, you can post comments to Jira, Asana, and GitHub tickets. The skill extracts the specific backend reference—jira_ref, asana_ref, or gh_ref—from the wiki page to route the comment to the correct external platform.

How does the audit log work when posting comments to external tickets?

The audit log updates automatically after a comment is successfully posted to an external ticket. The workflow records the CLI action, ensuring a verifiable trail for all comments published from wiki pages.

What happens if a wiki page is missing a backend reference for the external ticket?

If a wiki page is missing a backend reference, the skill cannot post the comment. It explicitly requires resolving a valid gh_ref, jira_ref, or asana_ref from the wiki task page before initiating the posting workflow.