git-commit

Create well-structured git commits with conventional commit messages. Use when asked to commit changes, prepare a commit, or stage and push code.

Ir a la instalación

Repositorio: agulli/atlas-agents
Última actividad en el origen: 13 de mayo de 2026 a las 10:10
Idioma detectado de SKILL.md: inglés
Estrellas: 492
Forks: 104

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/agulli/atlas-agents --skill git-commit

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Revisa los archivos de origen

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

Volver a la búsqueda Volver a la instalación

api-design

Design or review REST and GraphQL API interfaces. Use when asked to design an API, review endpoint structure, define request/response schemas, or improve API ergonomics.

2026-05-13

code-review

Perform a structured security and quality audit on source code. Use when asked to review code, audit a pull request, check for vulnerabilities, or assess code quality.

2026-05-13

data-pipeline

Design, build, or debug data processing pipelines. Use when asked to process a dataset, transform data, build an ETL pipeline, schedule batch jobs, or fix data quality issues.

2026-05-13

Ver todos los de este repositorio

name	git-commit
description	Create well-structured git commits with conventional commit messages. Use when asked to commit changes, prepare a commit, or stage and push code.
license	MIT
compatibility	Requires git
allowed-tools	Bash(git:*)

Process

Run git status to see all changed files. Read the output carefully.
Run git diff --stat to understand the scope of the change.
Group related changes. If the diff contains unrelated changes (e.g., a bug fix AND a new feature), create separate commits. Do not bundle unrelated work.
Stage files intentionally. Use git add <specific-files>, never git add . unless every changed file belongs in the same logical commit.

Write the commit message using Conventional Commits format:

<type>(<scope>): <description>

<body — explain WHY, not WHAT>

<footer — references, breaking changes>

Types: feat, fix, refactor, docs, test, chore, perf, ci

Verify before committing. Run git diff --cached to review exactly what will be committed. Read the staged diff.
Commit. Run git commit -m "..." with the message.

Rationalizations

Excuse	Rebuttal
"I'll just use `git add .` to save time"	Staging everything blindly leads to committing debug files, env vars, and unrelated changes. Stage intentionally.
"The message 'fix stuff' is fine for now"	Every commit message is permanent history. Write it properly the first time.
"I'll squash these later"	You won't. Write clean commits now.

Verification

git diff --cached output was reviewed before committing
Commit message follows Conventional Commits format
No unrelated changes were bundled into a single commit
No .env, __pycache__, or build artifacts were staged

git-commit

Datos de origen

Opciones de instalación

Revisa los archivos de origen

Más de este repositorio

Más de este repositorio

Process

Rationalizations

Verification

Process

Rationalizations

Verification