Receber por email
← Voltar para o catálogo

atomic-commit-and-push

Run the atomic-commit workflow on the current changes, then publish the resulting commits to the remote. Use whenever the user says \"commit and push\", \"ship these changes\", \"atomic commit and push\", \"publish my work\", or wants atomic commits delivered to origin in one step. Prefers `git submit` (git-branchless); falls back to a named branch + `git push origin HEAD:refs/heads/<branch>`. Ref

27estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: Apache-2.0

Como adicionar

/plugin marketplace add OutlineDriven/odin-claude-plugin

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/atomic-commit-and-push/svg)](https://www.skillteca.com.br/skills/atomic-commit-and-push)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

Atomic Commit and Push

Phase 1 — Atomic commit

Review staged + unstaged changes. Group by mechanism/file boundary. Create one commit per logical change. Run repo-native type-checker and linter before each commit. Do NOT bundle unrelated changes.

Phase 2 — Publish

Prefer git submit when git-branchless is installed and the forge is supported. Fallback: pick a descriptive branch name, then git push origin HEAD:refs/heads/<branch>. Set upstream only when the user explicitly wants tracking. Never --force or --force-with-lease without explicit user authorization. Never push directly to protected branches (e.g., main, master, release/*).

Compartilhar X LinkedIn