Receber por email
← Voltar para o catálogo

merge-and-release

Reference document describing merge prerequisites (approval, CI checks, mergeable, conversations resolved, stale approval), release versioning (semantic semver), and changelog generation. Explains why Tier 3 confirmation is structural: merge and release cost is borne by downstream people. Reference only (`disable-model-invocation: true`); consumed by `/flow:merge` and `/flow:release`.

5estrelas
Atualizado há 5 meses

Ver no GitHub ↗

Como adicionar

/plugin marketplace add synaptiai/synapti-marketplace

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/merge-and-release/svg)](https://www.skillteca.com.br/skills/merge-and-release)
#ai

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 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

Merge and Release

Reference document for merge and release policy. The executable bash lives in plugins/flow/commands/merge.md and plugins/flow/commands/release.md. This skill describes what those commands enforce and why.

Both merge and release are Tier 3 — they always require explicit human confirmation, even in autonomous mode. This is non-negotiable.

Iron Law

**MERGE IS IRREVERSIBLE IN PRACTICE. Treat every merge as permanent. Every prerequisite must be verified with fre

[Description truncada. Veja o README completo no GitHub.]

Compartilhar X LinkedIn