work_git_git-finish

Commit, push, and document coding session changes on GitHub.

1|Updated Apr 16, 2026
One-click install
npx skills add https://github.com/JoNaYeon/claude-code-skills --skill work-git-git-finish
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work_git_git-finish
Source: https://github.com/JoNaYeon/claude-code-skills/tree/main/work/git/work_git_git-finish
Command: npx skills add https://github.com/JoNaYeon/claude-code-skills --skill work-git-git-finish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates finalizing a coding session by committing changes, pushing to the current branch, and documenting work via GitHub Issues when requested.

Core Features & Use Cases

  • Safe, selective staging and exclusion of sensitive files to prevent accidental leakage.
  • Generate conventional commit messages and push to origin on the current branch.
  • Optional creation of GitHub Issues with a concise summary of changes and next steps, enabling traceability.
  • Produces a final status report that can be shared with teammates.

Quick Start

Finish my current feature by reviewing changes, staging verified files, committing with a conventional message, pushing to the current branch, and creating a GitHub Issue if needed.

Frequently Asked Questions about work_git_git-finish

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

FAQPage Schema
How do I automate git commit, push, and GitHub issue creation at the end of a coding session?

You can automate this workflow using a skill that safely stages verified files, generates conventional commit messages, pushes to the current branch, and optionally creates a GitHub Issue with a concise summary of changes and next steps.

What is a conventional commit workflow and how does it handle sensitive files?

A conventional commit workflow structures commit messages based on change type. This process enforces strict exclusions for sensitive files to prevent accidental leakage and uses diff summaries to accurately describe staged changes.

Can I automatically generate a GitHub Issue from my staged git changes?

Yes, you can automatically create a GitHub Issue from your staged git changes. The workflow generates an issue containing a concise summary of your changes and next steps, enabling project traceability.

Does this git commit and push workflow integrate with pull request creation?

Yes, this git commit and push workflow can integrate with a PR-creation workflow. After staging and pushing to the current branch, it produces a final status report and can transition into pull request creation.

How do I prevent accidental leakage of sensitive files when staging git changes?

To prevent accidental leakage of sensitive files when staging git changes, the workflow enforces selective staging and strict file exclusions before generating a conventional commit message and pushing to origin.