commit

Automate git staging, semantic commits, and remote pushes.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill commit-tecnologia-ibtech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: commit
Source: https://github.com/tecnologia-ibtech/geo-codex/tree/main/geo-git/skills/commit
Command: npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill commit-tecnologia-ibtech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the Git workflow for staging changes, creating semantic commits, and pushing to the remote, reducing manual overhead and mistakes.

Core Features & Use Cases

  • Inspect repository state and diffs to determine what to commit.
  • Create semantic commits following Conventional Commits and push changes to remote, enabling clean PRs.
  • Guardrails enforce commit messages and optional checks for special folders like .claude/ before pushing.

Quick Start

Instruct Claude to analyze the current git state, create semantic commits, and push to the remote.

Frequently Asked Questions about commit

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

FAQPage Schema
How do I automate semantic commits and push to remote?

To automate semantic commits and push to remote, this Skill inspects your git state, stages changes, creates Conventional Commits messages, and pushes to the remote repository automatically. It reduces manual overhead while ensuring clean PRs.

What are Conventional Commits and how do they work with git workflow automation?

Conventional Commits provide a standardized format for commit messages. This Skill applies them during git workflow automation by inspecting diffs, generating compliant messages, and managing feature branches with guardrails to enable clean review workflows.

Do I need any dependencies to automate git commits and pull request creation?

No dependencies are required to automate git commits and pull request creation. The Skill operates independently to inspect repository state, stage code changes, and push to the remote without needing external modules or components.

Can I use this to check for .claude folder changes before pushing?

Yes, you can check for .claude folder changes before pushing. The Skill includes guardrails that enforce commit message rules and perform optional checks for special folders like .claude/ to ensure safe remote pushes.

What is the best way to manage feature branches and inspect diffs before committing?

The best way to manage feature branches and inspect diffs is using automated guardrails. This Skill inspects repository state, reviews diffs to determine changes, and manages feature branches while enforcing Conventional Commits standards before pushing.

Why does automated commit generation fail to follow Conventional Commits standards?

Automated commit generation fails when guardrails are bypassed. This Skill enforces Conventional Commits standards by inspecting repository diffs and applying message rules, preventing non-compliant commits from being pushed to the remote.