close

Draft a closing comment, update wiki status, and transition linked backends.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/brandtam/rubber-ducky --skill close-brandtam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: close
Source: https://github.com/brandtam/rubber-ducky/tree/main/src/skills/close
Command: npx skills add https://github.com/brandtam/rubber-ducky --skill close-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Close a task: draft a resolution comment, optionally sync with each linked backend, set wiki to done, and redirect to next active task.

Core Features & Use Cases

  • Draft and post a concise closing comment for a task, ensuring readers understand what was done and why.
  • Update the wiki status to done and optionally apply transitions to linked backends (GitHub, Jira, Asana).
  • Redirect to the next active task or prompt for follow-up work when none is obvious.

Quick Start

Describe the task to close or provide its wiki path and ask rubber-ducky to perform a complete close workflow.

Frequently Asked Questions about close

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

FAQPage Schema
How do I close a task and sync the status across GitHub, Jira, and Asana backends?

To close a task and sync backends, draft a closing comment, update the wiki status to done, and apply transitions to linked GitHub, Jira, and Asana targets through a confirmation flow.

What is the best way to draft a closing comment for an issue linked to multiple external backends?

Drafting a closing comment for linked backends involves generating a concise resolution note that explains what was done, previewing it before posting, and transitioning the wiki and external backends as needed.

Can I automatically transition a Jira ticket to done by closing a linked wiki page task?

Yes, closing a linked wiki page task can transition a Jira ticket to done by applying backend transitions through a confirmation flow, ensuring the task status synchronizes across the wiki and Jira.

How does the workflow handle redirecting to the next active task after closing the current one?

After closing a task and updating backends, the workflow redirects to the next active task or prompts for follow-up work when no obvious next task is available.

Does closing a task with this workflow post the resolution comment automatically without review?

No, closing a task does not post the resolution comment automatically; the workflow previews the drafted closing note before posting to ensure readers understand what was done and why.

What backends are supported for task status synchronization when closing a wiki page?

Supported backends for task status synchronization when closing a wiki page include GitHub, Jira, and Asana, which are updated as needed through a confirmation flow alongside the wiki status.