Safe Multi-Session Deploy
Madwr1d/safe-multi-session-deploy
Deploys seguros para múltiplas sessões de agentes no mesmo repositório
Ver no GitHubSkill para Claude/agents que garante deploys seguros quando múltiplas sessões de agentes compartilham a mesma árvore de trabalho. Previne sobrescrita de edições, deploys em projetos errados e perda de rastreabilidade de proveniência através de guardas pré-deploy e merge explícito com detecção de conflitos.
Instalação
npx convez-ai Madwr1d/safe-multi-session-deploy1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Coordenar deploys de múltiplas sessões de agentes em um mesmo projeto
- Evitar sobrescrita acidental de edições em progresso durante deploy
- Garantir rastreabilidade de qual sessão/build está vivo em produção
- Prevenir deploy em projeto Vercel errado ou desatualizado
Veredito

Solução robusta e production-ready para um problema real de equipes rodando múltiplas sessões de IA simultaneamente. Implementa guardas técnicas sólidas (verificação de projeto, commit tagging, merge explícito, validação pós-deploy) que compensam a falta de sincronização nativa entre agentes.
README
A tradução para o português deste README ainda está na fila.
safe-multi-session-deploy
A Claude Code / agent skill that makes deploying safe when multiple agent sessions share one working tree — the situation that quietly breaks real teams running several AI coding sessions at once.
It prevents the three failure modes that actually happen in production:
- Clobbering unsaved work — a deploy uploads the whole working tree, so another session's in-progress edits ship (or yours get overwritten).
- Wrong-project deploy —
.vercel/project.jsonis linked to a stale or duplicate project, so the build succeeds but the real site never updates and you think you shipped. - Invisible provenance — after a deploy you can't tell which session's build is actually live, or whether the alias even moved.
It also includes the git-native version of "merge every session's work into one build before shipping" (per-session branches → integration branch → real 3-way merge with conflict detection → verified deploy).
Install
npx skills add Madwr1d/safe-multi-session-deploy
Then it's available to your agent like any other skill. (It shows up on skills.sh via install telemetry.)
What's inside
SKILL.md— the rules an agent follows: identify a session id, session-tag commits, the pre-deploy guard checklist, and the integration-branch workflow.scripts/deploy-guard.sh <domain> [project] [public-dir]— single-session safe deploy for Vercel: verifies the linked project owns the domain, checks for foreign uncommitted edits, builds as a gate, stampsversion.json{session, sha, builtAt, project}, deploys, then verifies the liveversion.jsonmatches what it built.scripts/integrate-and-deploy.sh <domain> <project>— merges everysession/*branch into oneprebranch (stops on conflict instead of silently clobbering), stamps multi-session provenance, deploys, and verifies live.
Why
Born from a real incident: four agent sessions on one repo, a deploy that went to the wrong Vercel project, and no way to tell whose code was live. This skill is the checklist + scripts that stop all three.
License
MIT