push

Push wiki task pages to external ticket backends with confirmation gating and audit logging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It removes the manual copy-paste work of turning a local markdown task page into a ticket in an external tracker like GitHub, Jira, or Asana, while preventing accidental or duplicate external writes through a mandatory confirmation gate. ## Core Features & Use Cases - Draft-to-ticket workflow: Reads a wiki task page, drafts a backend-specific ticket via a ticket-writer agent, and walks the user through any missing fields before pushing. - Confirmation-gated writes: Every external write requires a confirm-token consumed by the rubber-ducky push CLI, so no ticket is created without explicit user approval. - Automatic bookkeeping: Stamps backend refs on the task page, posts cross-reference back-link comments between backends, appends audit-log lines, and rebuilds the index. - Use Case: You have a wiki/tasks/fix-login-bug.md page and want it tracked in Jira. The skill drafts the ticket, shows a preview, asks for confirmation, pushes it, and links both sides automatically. ## Quick Start Ask the assistant to push the task page wiki/tasks/fix-login-bug.md to your configured ticket backend and confirm the preview when prompted.

Frequently Asked Questions about push

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

FAQPage Schema
How do I push a markdown task page to Jira or GitHub as a ticket?▼

Provide the task page path as the argument. The skill reads the page, drafts a ticket using the backend template, shows a preview, and pushes it via the rubber-ducky CLI after you confirm the token prompt.

How do I create tickets from Obsidian notes automatically?▼

Store tasks as typed markdown pages in the vault, then run the push workflow with the page path. The CLI creates the ticket in your configured backend and stamps the backend reference back onto the note.

Can the push happen without my confirmation?▼

No. The skill is risk_class hard, and the external write only happens through rubber-ducky push with a valid confirm-token. If the token is missing, expired, or mismatched, the CLI exits without making any external call.

What happens if the ticket creation fails after I confirm?▼

If the backend create call fails, the CLI exits non-zero and no wiki frontmatter is updated. The error is surfaced to you, and a retry requires requesting a fresh confirmation token.

Does pushing a task twice create duplicate tickets?▼

The skill warns you if the task page already has a backend reference such as gh_ref, jira_ref, or asana_ref, indicating it may already exist in the target system before you confirm another push.