commit

Estrellas10

Forks7

Actualizado26 de marzo de 2026 a las 16:26

Stage all changes, generate a commit message from the diff, and commit. Optionally push.

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.

Fuente

G-Research

G-Research/bobbit

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

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

SKILL.md

readonly

name	commit
description	Stage all changes, generate a commit message from the diff, and commit. Optionally push.
argument-hint	["push"]

Commit the current changes with an auto-generated message.

Steps

Run git add -A to stage all changes
Run git diff --cached --stat to see what changed
Run git diff --cached to read the full diff
Write a concise, conventional-commits-style commit message based on the diff:
- Use the format: type: summary (e.g. feat:, fix:, refactor:, test:, docs:, chore:)
- First line under 72 characters
- Add a blank line then bullet points for notable details if the change is non-trivial
- Do NOT pad or over-explain — be direct
Run git commit -m "<message>"
If the argument is "push", also run git push

Rules

If there are no staged changes after git add -A, say so and stop.
Never amend a previous commit — always create a new one.
Do not ask for confirmation — just commit.

Más de este repositorio

mismo repositorio

release

G-Research/bobbit

Cut a Bobbit release — preflight checks, version bump, signed tag (CI publishes the root to npm via OIDC on tag push), optional binary sub-packages, GitHub release with generated notes.

2026-07-2810

prw-preview

G-Research/bobbit

Bring up a like-for-like PR Walkthrough panel preview using the exact pack source and Bobbit theme bridge

2026-06-2810

client-debug

G-Research/bobbit

Pull diagnostics out of the running web client (env, viewport/safe-area, performance, app state) and debug hard-to-inspect mobile / installed-PWA layout bugs

2026-06-0810

html

G-Research/bobbit

Build an interactive HTML UI in the live preview panel using Bobbit's design system

2026-06-0710

html

G-Research/bobbit

Build an interactive HTML UI in the live preview panel using Bobbit's design system

2026-06-0710

mockup

G-Research/bobbit

Create a high-fidelity interactive HTML design mockup with live preview

2026-06-0710

name	commit
description	Stage all changes, generate a commit message from the diff, and commit. Optionally push.
argument-hint	["push"]

Commit the current changes with an auto-generated message.

Steps

Run git add -A to stage all changes
Run git diff --cached --stat to see what changed
Run git diff --cached to read the full diff
Write a concise, conventional-commits-style commit message based on the diff:
- Use the format: type: summary (e.g. feat:, fix:, refactor:, test:, docs:, chore:)
- First line under 72 characters
- Add a blank line then bullet points for notable details if the change is non-trivial
- Do NOT pad or over-explain — be direct
Run git commit -m "<message>"
If the argument is "push", also run git push

Rules

If there are no staged changes after git add -A, say so and stop.
Never amend a previous commit — always create a new one.
Do not ask for confirmation — just commit.