Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

Comenzar

git-commit

Estrellas30

Forks5

Actualizado14 de abril de 2026 a las 11:15

Git commit workflow. Use when asked to commit changes or on the word `commit`.

Instalación

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.

Ejecutar en Manus

Fuente

juanibiapina

juanibiapina/dotfiles

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	git-commit
description	Git commit workflow. Use when asked to commit changes or on the word `commit`.

Git Commit

Commit only when the user explicitly asks.

Review staged, unstaged, and untracked changes plus recent commit style. Draft a concise message that explains why. Stage the right files, commit, then verify with git status.

Safety rules

NEVER update git config
NEVER run destructive commands unless explicitly requested
NEVER skip hooks unless explicitly requested
NEVER push unless explicitly asked
NEVER force push to main or master
NEVER use interactive git flags
Do not create empty commits
Do not commit likely secrets

Amend rules

Use --amend only when all are true:

the user explicitly asked, or a successful commit auto-modified files via hooks
the HEAD commit was created by you in this conversation
the commit has not been pushed

If a hook fails, fix the issue and create a new commit.

Más de este repositorio

mismo repositorio

mcpli

juanibiapina/dotfiles

CLI tool for interacting with MCP (Model Context Protocol) servers. Use when invoking MCP tools, managing MCP servers, or working with MCP-based APIs. Triggers on "MCP server", "mcpli", "invoke MCP tool", or any MCP server interaction.

2026-07-1130

code

juanibiapina/dotfiles

Use when executing a plan or implementing a coding task. Turns a plan or clear request into working code, tests, and verification.

2026-07-0930

research

juanibiapina/dotfiles

Use for researching, checking facts, looking things online, comparing options, etc.

2026-07-0830

plan

juanibiapina/dotfiles

Use when asked to plan a coding task. Produces a written implementation plan (research plus steps) for a code change.

2026-07-0830

git-rebase

juanibiapina/dotfiles

Use before performing a rebase or resolving rebase conflicts.

2026-07-0530

open-pr

juanibiapina/dotfiles

Use when opening a pull request, pushing changes for review, or when the user says "open PR", "create PR", "send for review", or "get this merged".

2026-06-3030

name	git-commit
description	Git commit workflow. Use when asked to commit changes or on the word `commit`.

Git Commit

Commit only when the user explicitly asks.

Review staged, unstaged, and untracked changes plus recent commit style. Draft a concise message that explains why. Stage the right files, commit, then verify with git status.

Safety rules

NEVER update git config
NEVER run destructive commands unless explicitly requested
NEVER skip hooks unless explicitly requested
NEVER push unless explicitly asked
NEVER force push to main or master
NEVER use interactive git flags
Do not create empty commits
Do not commit likely secrets

Amend rules

Use --amend only when all are true:

the user explicitly asked, or a successful commit auto-modified files via hooks
the HEAD commit was created by you in this conversation
the commit has not been pushed

If a hook fails, fix the issue and create a new commit.