commit

Create a conventional commit from local changes and push the feature branch to origin.

Updated Mar 19, 2026

Search Tags:#git #commit #push #branch #conventional-commit #co-authored-by

Ready to run

npx skills add https://github.com/japurcell/skills --skill commit-japurcell

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/japurcell/skills/tree/main/skills/commit
Command: npx skills add https://github.com/japurcell/skills --skill commit-japurcell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning multiple local changes into a single, clean git commit and pushing the resulting feature branch to origin, reducing manual steps and mistakes.

Core Features & Use Cases

Stage intended changes, create or reuse a feature branch, and compose a conventional commit that can link to issues and include Co-authored-by trailers.
Push the feature branch to origin with upstream tracking and return a concise summary of the branch and commit details.
Handle optional issue linkage gracefully and provide a deterministic workflow suitable for collaborative code reviews.

Quick Start

Commit the current workspace changes into a single atomic conventional commit on a feature branch and push it to origin.

Frequently Asked Questions about commit

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

FAQPage Schema

How do I commit local git changes and push to origin in one step?▼

To commit and push in one step, this workflow stages local changes, creates a conventional commit on a feature branch, and pushes it to origin with upstream tracking automatically.

What is a conventional commit and how does co-authored-by work?▼

A conventional commit uses a structured message format for clean history. The workflow can append co-authored-by trailers to attribute work to multiple contributors deterministically.

Can I link a git issue to my feature branch commit automatically?▼

Yes, you can link issues in your commit. The workflow handles optional issue linkage gracefully, embedding references directly into the conventional commit message during creation.

Does this workflow create a pull request after pushing the branch?▼

No, it does not create a pull request. The workflow guards against PR creation, focusing solely on atomic commits and pushing the feature branch to origin for collaborative review.

Why use an atomic commit workflow for local git changes?▼

An atomic commit workflow ensures local changes are bundled into a single clean commit. This reduces manual steps and mistakes while providing a deterministic branch history for code reviews.