finish-task

Commit staged changes, push to main, and close GitHub issues.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/sogadaiki/claude-code-skills --skill finish-task-sogadaiki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: finish-task
Source: https://github.com/sogadaiki/claude-code-skills/tree/main/skills/finish-task
Command: npx skills add https://github.com/sogadaiki/claude-code-skills --skill finish-task-sogadaiki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of finalizing a development task by committing changes, pushing them to the main branch, and closing associated issues, ensuring a clean and updated project state.

Core Features & Use Cases

  • Automated Committing & Pushing: Stages and commits all changes with a standardized message format and pushes them to the main branch.
  • Issue Management: Closes GitHub issues when a task is completed, linking commits to issue tracking.
  • Session Persistence: Updates a restart.md file to save session progress and logs work done in a dedicated logs/ directory.
  • Use Case: After completing a feature, run this Skill to finalize your work, update project tracking, and prepare for the next task or a code review.

Quick Start

Run the finish-task skill to commit and push your current changes to the main branch and close issue number 123.

Frequently Asked Questions about finish-task

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

FAQPage Schema
How do I automate git commit, push to main, and close GitHub issues in one step?▼

You can automate git commit and push to main while closing associated GitHub issues by running a task finalization workflow that stages changes, commits with a standardized message, and syncs to origin. This links your commits directly to issue tracking and updates project logs.

What is the best way to save session progress and log work details after completing a git task?▼

Saving session progress and logging work details after completing a git task involves updating a restart.md file for persistence and writing structured entries into a dedicated logs directory. This ensures your project state is recorded for the next session or code review.

Does this task completion workflow support branch-based pull requests instead of committing directly to main?▼

Yes, the task completion workflow supports both direct main branch commits and a parallel workflow for branch-based pull requests. You can choose to push your staged changes directly to main or route them through a branch for review.

Can I link my git commits to GitHub issues automatically when finalizing a development task?▼

You can link git commits to GitHub issues automatically when finalizing a development task by specifying the issue number during the commit process. The workflow closes the associated GitHub issues once the changes are pushed to origin.

Do I need to manually stage changes before running an automated git commit and push workflow?▼

No, you do not need to manually stage changes before running the automated git commit and push workflow. The process handles staging all changes, committing them with a standardized message, and pushing directly to the main branch.

When should I avoid committing directly to the main branch during task completion?▼

You should avoid committing directly to the main branch during task completion when your project requires code review before merging. In this case, use the parallel branch-based pull request workflow instead of the direct main branch commit path.