commit

Stage and commit changes with a clear, concise commit message.

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/antiwork/gumroad --skill 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.

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

name	commit
description	Stage and commit changes with a clear, concise commit message.
argument-hint	["optional message hint"]
allowed-tools	Bash(git *)

Create a commit for the current changes.

Run git status (without -uall) to see untracked and modified files.
Run git diff and git diff --cached to understand staged and unstaged changes.
Run git log --oneline -5 to see recent commit style.
Run bin/test-confidence to verify your changes don't break anything. Opus analyzes your diff and runs the right tests. Wait for 99% confidence (green bar) before proceeding. If any test fails, fix it first.
Run linters on changed files before staging:
- Ruby files: bundle exec rubocop --force-exclusion -a <files>
- JS/TS files: npm run lint-fast -- --max-warnings 0 --fix --no-warn-ignored <files>
- TypeScript type check: npx tsc --noEmit (required, catches type errors that eslint skips)
- CSS/SCSS/JSON/MD files: npx prettier --write <files>
- SVG files: npx svgo --multipass <files>
- Fix any lint errors or type errors before proceeding. Do not commit code that fails linting or type checking.
Stage the relevant files by name — avoid git add -A or git add ..
Write a commit message and commit.

If $ARGUMENTS is provided, use it as a hint for the message.

Use the imperative mood ("Add", "Fix", "Remove", not "Added", "Fixes", "Removed").
Be concise: one short sentence, ideally under 50 characters.
Do NOT use conventional commit prefixes (no feat:, fix:, chore:, etc.).
Do NOT add any Co-Authored-By or similar trailers.
Focus on what changed and why, not how.
If a second line is needed for context, keep it brief.

$ARGUMENTS