close-task

Commit staged changes, transition Jira tickets to resolved, log work, and capture lessons.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/daudaudinang/vibecode --skill close-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: close-task
Source: https://github.com/daudaudinang/vibecode/tree/main/.agents/skills/close-task
Command: npx skills add https://github.com/daudaudinang/vibecode --skill close-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the end-to-end process of closing a task by committing code changes, transitioning Jira tickets to resolved, logging work, and capturing lessons learned.

Core Features & Use Cases

  • Selective Git Staging: Stage only task-related files (not all files)
  • Conventional Commit: Create properly formatted commit messages
  • Jira Transition: Move ticket to resolved status
  • Log Work: Record time spent with a worklog entry
  • Lesson Capture: Run lesson-capture to document learnings

Quick Start

Close-task PRES-28 by staging only task-related files, making a conventional commit, transitioning the Jira ticket to resolved, logging the work, and capturing lessons learned.

Frequently Asked Questions about close-task

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

FAQPage Schema
How do I automate committing code changes, updating Jira ticket status, and logging work time together?

This Skill automates closing tasks by committing code changes, transitioning Jira tickets to resolved status, logging work time, and capturing lessons learned. It stages only task-related files and formats commit messages conventionally.

How to stage only task-related files for a conventional commit linked to a Jira ticket?

You can stage only task-related files selectively, avoiding unrelated changes. The Skill then creates a conventional commit message before transitioning the Jira ticket to resolved and logging work.

Can I log work time and capture lessons learned when transitioning a Jira ticket to resolved?

Yes, the Skill logs work time with a worklog entry and runs lesson-capture to document learnings while transitioning the Jira ticket to resolved. Optional time tracking is supported during the task closure process.

Does this task closure workflow require any specific Git or Jira plugins to function?

No specific plugins are required. The Skill operates independently without dependencies to orchestrate selective staging, conventional commits, Jira transitions, worklog entries, and lesson-capture.

What is the best way to link code commits to Jira issues and document project learnings simultaneously?

An orchestrated task closure workflow links code commits to Jira issues by staging related files, making conventional commits, transitioning tickets to resolved, and capturing lessons. This ensures traceability and knowledge documentation.