git-commit

Inspect Git changes, generate FEAT/FIX/DOCS messages, and push commits.

1|Updated Sep 6, 2024
One-click install
npx skills add https://github.com/carlos18bp/gym_project --skill git-commit-carlos18bp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit
Source: https://github.com/carlos18bp/gym_project/tree/main/.agents/skills/git-commit
Command: npx skills add https://github.com/carlos18bp/gym_project --skill git-commit-carlos18bp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of creating consistent Git commits by inspecting current working-tree changes, generating a professional FEAT/FIX/DOCS message, and pushing the result automatically.

Core Features & Use Cases

  • Change inspection (status + diff): Detects whether the current repo has uncommitted changes and inspects what changed.
  • Conventional commit message generation: Creates an English commit message with a FEAT/FIX/DOCS prefix based on the diff contents.
  • Safe execution flow (stage → commit → push): Stages only relevant changes, commits once per repo, and pushes to the configured remote/branch while continuing if a push fails.
  • Optional multi-repo automation: With --all, iterates over local repos on the host (LOCAL_PROJECTS plus vps-ops-toolkit), skipping clean repos.

Quick Start

Run the command to commit and push the changes in your default toolkit repo: /git-commit.

Frequently Asked Questions about git-commit

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

FAQPage Schema
How do I generate conventional commit messages automatically from git diff?

To generate conventional commit messages automatically, this Skill inspects your local repository's git status and git diff, stages relevant files, composes a FEAT/FIX/DOCS prefixed message based on the changes, and then executes git commit and git push.

What is the best way to automate staging, committing, and pushing changes for multiple local git repositories?

The best way to automate multi-repo commits is using the --all flag, which iterates over eligible local Git projects, skips clean repositories, stages relevant changes, commits once per repo, and pushes to the configured remote branch while continuing if a push fails.

Can I use this to push commits to a specific remote branch without manual git push commands?

Yes, you can push commits without manual commands. The Skill safely handles remote and branch configuration by executing git commit and git push automatically, continuing the iteration flow even if an individual push operation fails.

Does the git-commit Skill require any external dependencies or CI-CD integrations to function?

No external dependencies or CI-CD integrations are required. The Skill operates independently by running local git commands to inspect working-tree changes, stage relevant files, commit with a conventional prefix, and push to your configured remote.

Why does my automated conventional commit skip certain local repositories?

Automated conventional commits skip repositories that have no uncommitted changes. When iterating with --all, the Skill detects clean working trees and safely bypasses them, committing and pushing only in eligible local Git projects with actual modifications.