skills.rest
bbenefield89
bbenefield89COMMUNITY
Explore all skills by this author →
WebsiteGitHub

close-task

Commits local changes and closes an approved GitHub Task while marking its parent Ticket completed.

Updated Jul 7, 2026
Search Tags:#code review#task management#workflow automation#github#gh cli#git commit#issue closure
One-click install
npx skills add https://github.com/bbenefield89/skills --skill close-task-bbenefield89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: close-task
Source: https://github.com/bbenefield89/skills/tree/main/skills/close-task
Command: npx skills add https://github.com/bbenefield89/skills --skill close-task-bbenefield89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a delivered GitHub Task is reviewed and approved, developers still need to manually commit local changes, close the issue with the correct reason, and update the parent Ticket's task table. This Skill automates that closure workflow with verification at every step. ## Core Features & Use Cases - Local Commit Procedure: Stages all tracked, deleted, and untracked changes except explicit user exclusions, then creates a conventional commit without pushing. - GitHub Task Closure: Closes the resolved Task with the completed reason via the GitHub CLI or API, verifying state CLOSED and reason COMPLETED. - Parent Ticket Update: Appends a completed marker to the exact Task entry in the parent Ticket's generated tasks table or task list, preserving all surrounding content byte-for-byte. - Use Case: After running /deliver #65 and receiving approval, invoke this Skill to commit the work, close issue #65 as completed, and mark its entry completed on the parent Ticket. ## Quick Start Close task #65 now that the delivery has been reviewed and approved.

Frequently Asked Questions about close-task

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

FAQPage Schema
How do I close a GitHub issue as completed with the gh CLI?▼

Use gh issue close <number> --repo <owner/repo> --reason completed to close an issue with the completed reason. This Skill runs that command, then re-reads the issue to verify state CLOSED and reason COMPLETED before updating the parent Ticket.

How do I commit changes but exclude specific files?▼

State your exclusions explicitly when requesting closure. The Skill stages all tracked, deleted, and untracked changes except your exclusions, removes excluded files from the index, and preserves their working-tree content.

Does closing a task push commits or close the parent ticket?▼

No. The Skill creates a local conventional commit only and never pushes, merges, or comments. The parent Ticket stays open or closed as found, even when the closed Task was its last unfinished child.

What happens if the task is already closed or the parent entry is missing?▼

If the Task is already closed as completed, the Skill skips closure and repairs only a missing parent marker. If the parent or entry is missing, duplicated, or conflicts with the configured relationship, it stops and reports the mismatch before any mutation.

Can I close a task without prior delivery approval?▼

No. Closure requires explicit review approval in the conversation, such as "approved, close #65". Without it, the Skill prepares the exact changes and asks whether the delivered Task is approved for closure.

Related Skills

Explore More Software Engineering Skills→
Hoang604Hoang604

discuss-plan

Review and refine a phase plan in PLAN.md before execution.

Community
Advanced
arjitj2arjitj2

resolve-merge-conflicts

Resolves pull request merge conflicts by merging the base branch and pushing the updated branch.

Community
Advanced
Knuckles-TeamKnuckles-Team

spec-to-backlog

Convert Confluence specifications into Jira Epics and linked tickets.

Official
Intermediate
Lia-CreativeLia-Creative
1

pickup

Guides agents through picking up and handing back Linear tickets using a defined reading order.

Official
Intermediate