AtomicCommit Pro

Analyze code hunks and generate Spanish Conventional Commits.

Updated Jan 16, 2026
One-click install
npx skills add https://github.com/milc3sar/AtomicCommit-Pro --skill atomiccommit-pro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: AtomicCommit Pro
Source: https://github.com/milc3sar/AtomicCommit-Pro/tree/main
Command: npx skills add https://github.com/milc3sar/AtomicCommit-Pro --skill atomiccommit-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Este Skill transforma cambios de código complejos en un historial de commits atómicos y semánticos, evitando commits monolíticos que dificultan la trazabilidad.

Core Features & Use Cases

  • Segmentación por contexto: separa cambios en commits según su intención (fix, feat, refactor) y evita mezclar lógicas distintas.
  • Seguridad y gobernanza: detecta archivos sensibles y garantiza que no se registren credenciales o datos sensibles.
  • Mensajes semánticos en español: genera mensajes de commit siguiendo Convencional Commits en español.

Quick Start

Guía rápida: solicita "guardar cambios" para activar la descomposición de un cambio complejo en commits atómicos y genera mensajes semánticos en español.

Frequently Asked Questions about AtomicCommit Pro

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

FAQPage Schema
How do I split complex changes into atomic commits using git?

Creating semantic commits involves generating messages that follow Conventional Commits standards in Spanish. This Skill formulates structured commit messages by analyzing the semantic intent of your staged code changes, ensuring your history remains organized and easily traceable.

How do I generate semantic commit messages in Spanish for my code changes?

Generating semantic commit messages in Spanish involves applying Conventional Commits standards to your staged changes. This Skill analyzes your code hunks to produce structured Spanish messages, categorizing intents like fixes or features for a traceable history.

How do I prevent mixing different logics or styles in a single commit?

Preventing mixed logics in a single commit requires granular staging of individual code hunks. This Skill analyzes your changes to separate distinct intentions, enforcing atomic commits that avoid combining unrelated bug fixes, features, or style adjustments together.

Can I use this atomic commit workflow with standard Git tooling?

Yes, you can use this atomic commit workflow with standard Git tooling. It requires no additional dependencies or specialized components, operating directly within your current environment to analyze code hunks and guide granular staging processes.

How do I avoid committing sensitive files or credentials when saving changes?

Avoiding sensitive files when saving changes requires governance checks before staging. This Skill includes security detection to identify sensitive data or credentials in your working directory, guaranteeing they are not recorded in your commit history.