command-task-done

Name: command-task-done
Availability: InStock
Author: aroido

Automates GitHub issue completion including PRs, checklists, and project board updates using gh, jq, rg.

Updated Apr 22, 2026

Search Tags:#automation #workflow #task management #pull request #github #issue tracking

Ready to run

npx skills add https://github.com/aroido/vibesmith --skill command-task-done

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: command-task-done
Source: https://github.com/aroido/vibesmith/tree/main/.codex/skills/command-task-done
Command: npx skills add https://github.com/aroido/vibesmith --skill command-task-done

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of completing a GitHub issue, including updating checklists, creating and reviewing pull requests, and managing project boards, streamlining the development workflow.

Core Features & Use Cases

Issue Completion: Closes GitHub issues and handles associated pull requests.
Workflow Automation: Automates steps like PR creation, review, merging, and project status updates.
Use Case: After finishing a coding task related to a GitHub issue, you can run this command to automatically create a PR, get it reviewed, merge it, and update the project board to 'Done'.

Quick Start

Execute the command-task-done skill with the GitHub issue number 123.

Frequently Asked Questions about command-task-done

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

FAQPage Schema

How do I automate closing a GitHub issue with pull requests and project board updates?▼

Automating GitHub issue closure requires managing pull requests, transitioning project boards, and updating checklists. This skill handles PR creation, review, merging, and status updates systematically to close issues and complete the development workflow.

Can I automatically move GitHub project board items to Done when a pull request merges?▼

Automating project board transitions to Done when a pull request merges is supported. The skill manages project status updates alongside PR creation and merging, ensuring GitHub issues are systematically closed and board states reflect completed development tasks.

Do I need GitHub CLI and jq to automate issue tracking and pull request workflows?▼

GitHub CLI (gh), jq, and rg are required dependencies for executing GitHub issue tracking and pull request automation. These tools enable the data manipulation and command execution necessary to manage checklists, PRs, and project board transitions.

What's the best way to manage GitHub workflow automation for systematic issue closure?▼

Managing GitHub workflow automation for systematic issue closure is best handled by automating the full sequence: PR creation, review, merging, and project board updates. This approach streamlines development workflows by closing issues and updating tracking systems in one process.

Does GitHub workflow automation handle checklist updates when completing a coding task?▼

GitHub workflow automation handles checklist updates when completing coding tasks. The skill updates issue checklists, creates and reviews pull requests, and manages project board transitions, ensuring all tracking elements reflect the completed work before closing the issue.

When should I not use automated GitHub issue closure for pull request management?▼

Automated GitHub issue closure should be avoided when workflows require manual review steps or custom project board configurations outside standard transitions. The automation applies to systematic issue closure and may not suit development processes needing human intervention or non-standard PR review rules.