skills.rest
brandtam
brandtamCOMMUNITY
Explore all skills by this author →
𝕏@brandtamGitHub

close

Closes tasks by drafting resolution comments, syncing backends, and updating wiki status.

2|1|Updated Apr 12, 2026
Search Tags:#task management#workflow automation#github#obsidian#jira#resolution comment#close task
One-click install
npx skills add https://github.com/brandtam/rubber-ducky-legacy --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-legacy/tree/main/src/skills/close
Command: npx skills add https://github.com/brandtam/rubber-ducky-legacy --skill close-brandtam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Closing a task usually means touching several systems at once — updating a wiki page, transitioning a ticket in an external tracker, and writing a resolution comment — which is repetitive and easy to do inconsistently. This Skill orchestrates the entire close-out flow so nothing is forgotten and every external write is confirmed before it happens. ## Core Features & Use Cases - Resolution comment drafting: Reads the task's activity log and body to draft a concise closing comment, which the user can approve, edit, or replace. - Multi-backend synchronization: Transitions the primary backend (GitHub, Jira, Asana) to done and posts the comment via confirm-token gated CLI calls, then optionally closes additional linked backends. - Atomic wiki update: Runs rubber-ducky task close to set status, closed date, daily page, and log in one operation, then redirects to the next active task. - Use Case: After fixing a login bug tracked in both your Obsidian vault and Jira, invoke the close flow to draft a summary comment, confirm the preview, transition the Jira ticket to done, and get redirected to your next in-progress task. ## Quick Start Ask the assistant to close a task by name or reference, for example: close the fix-login-bug task and post the resolution to its linked backend.

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 across my wiki and issue tracker at once?▼

Invoke the close flow with a task ref, wiki path, or title fragment. It drafts a resolution comment, shows a close preview, then updates the wiki via rubber-ducky task close and transitions the linked backend to done after your confirmation.

How do I post a closing comment to Jira or GitHub when finishing a task?▼

The close flow drafts a 2-4 sentence resolution comment from the task's activity log and posts it through the backend CLI using a confirm-token gate. A closing comment is always posted, though you can edit it before confirming.

Can I close a task in multiple linked backends at the same time?▼

Yes. After the primary backend closes, the flow asks separately about each additional linked ref. You can reuse the same closing comment or draft a new one for each backend before it transitions and posts.

What happens if the external tracker transition fails during task close?▼

If the primary backend transition fails before the wiki close, the wiki is not updated so the local state stays consistent with the external system. Failures on secondary linked backends only produce a warning without reversing the primary close.

Does closing a task write to external systems without confirmation?▼

No. Nothing is written externally until you approve the structured close preview, and each backend write requires a confirm token obtained through the rubber-ducky confirm request flow.

Related Skills

Explore More Software Engineering Skills→
brandtambrandtam
2

close

Closes tasks by drafting resolution comments, syncing backends, and updating wiki status.

Community
Advanced
ngochuy13ngochuy13

standup

Generate a structured yesterday/today/blockers standup update from work activity.

Community
Basic
anis-marrouchianis-marrouchi
4

update-issue

Update GitHub or GitLab issues to reflect Ralf story state changes.

Community
Intermediate
me2reshme2resh
489

spike-close

Close spike issues by promoting to Feature tickets or writing disposition memos.

Community
Advanced