git-commit-formatter

Enforce Conventional Commits format and automate atomic git operations.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/camilopiedra92/YNAB-Clone --skill git-commit-formatter-camilopiedra92
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-commit-formatter
Source: https://github.com/camilopiedra92/YNAB-Clone/tree/main/.agent/skills/git-commit-formatter
Command: npx skills add https://github.com/camilopiedra92/YNAB-Clone --skill git-commit-formatter-camilopiedra92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conventional commit discipline is enforced and Git operations are automated to ensure every change is tracked, formatted, and pushed with a single, reliable command sequence.

Core Features & Use Cases

  • Enforces Conventional Commits format on every commit attempt.
  • Automates the git:sync workflow to perform a single-atomic operation.
  • Supports commit, push, save, subir, and enviar workflows across locales.

Quick Start

Trigger the Autopilot one-turn command to run npm run git:sync with a Conventional Commits message.

Frequently Asked Questions about git-commit-formatter

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

FAQPage Schema
How do I enforce Conventional Commits format automatically in my git workflow?

Conventional Commits format is enforced automatically by validating message structure, scope, and length during commit, push, save, subir, or enviar requests, blocking unsafe commands while providing auditable outcomes.

What is the best way to automate git commit and push operations in a single step?

Automating git commit and push operations uses an autopilot one-turn script that runs a single-atomic git:sync workflow, ensuring changes are tracked, formatted, and pushed with one reliable command sequence.

Do I need a specific environment to run automated Conventional Commits validation?

Automated Conventional Commits validation runs within a controlled root environment using the autopilot one-turn script, executing npm run git:sync to apply formatting and atomic git operations safely.

Can I trigger git sync workflows using different language commands like subir or enviar?

Git sync workflows support commit, push, save, subir, and enviar command triggers across locales, applying Conventional Commits validation and atomic operations uniformly regardless of the command language used.

Why does my git commit get blocked during automated sync operations?

Git commits are blocked during automated sync when message structure, scope, or length fails Conventional Commits validation, or when unsafe commands are detected, ensuring safe auditable outcomes.