close-task

Finalizes tasks by running validation, marking merge requests ready, and updating task status.

Updated May 13, 2026
One-click install
npx skills add https://github.com/andrewcodesit/skills --skill close-task-andrewcodesit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: close-task
Source: https://github.com/andrewcodesit/skills/tree/main/skills/project-management/close-task
Command: npx skills add https://github.com/andrewcodesit/skills --skill close-task-andrewcodesit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Finishing a coding task involves scattered final steps—running validation, marking the merge request ready for review, collecting code-review findings, and updating task boards—that are easy to skip or do out of order, leaving unresolved issues hidden. ## Core Features & Use Cases - Final Validation Gate: Runs typecheck, lint, tests, or build before the task is closed, requiring fixes or explicit user acceptance of remaining risk. - Review Readiness & Findings Collection: Marks draft merge/pull requests ready for review and gathers findings from automated reviewers or local code-review reports. - Task Status Synchronization: Marks tasks done in local task files or connected project-management systems, and updates parent epic checklists when all children complete. - Use Case: After implementing a feature branch, ask the agent to wrap up—it validates the build, marks the existing draft MR ready for review, collects any automated reviewer comments, and marks the task done in your task board. ## Quick Start Ask the agent to finish and close the current task, including final validation and marking the merge request ready for review.

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 coding task after implementation?▼

Run final validation such as typecheck, lint, and tests, then mark the merge request ready for review and update the task status to done. The close-task workflow automates this sequence while requiring your confirmation for any remaining risks.

How to mark a draft merge request ready for review?▼

Use the connected git host's CLI or API to remove the draft flag from the existing merge or pull request. This signals the branch is complete and, in repos with automated reviewers, releases the held review.

Does closing a task require a code review first?▼

No, a code review is offered but not forced. If no automated reviewer or local review report exists, the workflow says so plainly and offers to run a review once, accepting your decision to close without one.

Can this update tasks in external project management tools?▼

Yes, it updates task status through the connected project-management tool when one is available. If no tool is connected, it tells you what remains to update manually, and it avoids transitioning issues that auto-close on merge.

What happens if validation fails when closing a task?▼

The workflow stops and either fixes the failures or asks for your explicit acceptance of the remaining risk. The task is only marked done after validation passes or you knowingly accept the outstanding issues.