ship
Skill0 starsChanged 6 months agoMITView on GitHub
Orquestra entrega de PR: verifica estado, roda check.ps1 (gate completo), push, cria PR com titulo do ultimo commit e lista de commits da branch. Sem argumento necessario.
- Commits and pushes
194 other projects use a version of this.
Adopted by
Most recently taken up by
- claudialnathan/skillstheir own version, first seen Nov 15, 2026
- saleem-hadad/skillstheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
- felipeam86/pipe-skillstheir own version, first seen Nov 15, 2026
- ShipfoxHQ/shipfoxtheir own version, first seen Nov 15, 2026
- nightly-labs/openbottheir own version, first seen Nov 14, 2026
Used with
Projects with it also use ios-sync, open-gstack-browser and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Saqlain-811Skillios-sync
Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)
Also in 6 projects that use this
seek888Skillopen-gstack-browser
Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".
Also in 10 projects that use this
ayudaySkillsetup-deploy
Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".
Also in 19 projects that use this
ShreyRaviSkilllanding-report
Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)
Also in 9 projects that use this
zebbernSkilldebug-fix
Find and fix a bug or issue — from any source (GitHub issue, error message, user report, or observed behavior)
Also in 4 projects that use this
ramybarsoumSkilldocument-release
Post-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped.
Also in 23 projects that use this
Other versions194 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 194
- garrytan/gstack★ 142ksame name
- rtk-ai/rtk★ 87ksame name
- simstudioai/sim★ 30ksame name
- millionco/react-doctor★ 15ksame name
- nightly-labs/openbot★ 7.9ksame name
- BuilderIO/agent-native★ 7.7ksame name
- fallow-rs/fallow★ 5.3ksame name
- puncsky/system-design-and-architecture★ 3.6ksame name
- plugin87/ux-ui-agent-skills★ 3.2ksame name
- ShenSeanChen/waku-agent★ 2.2ksame name
184 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository27 other files it gives its agents.
- frontend/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- frontend/CLAUDE.mdCLAUDE.md
- add-entity-to-auditSkill
- auditSkill
- babysit-prsSkill
- batchSkill
- daily-summarySkill
- factory-metricsSkill
- feature-frontSkill
- featureSkill
- init-projectSkill
- migrateSkill
- planSkill
- register-screenSkill
- review-archSkill
- review-frontSkill
- review-prSkill
- setup-architectureSkill
- setup-designSkill
- setup-infraSkill
- tasksSkill
- watch-ciSkill
- write-jobSkill
- write-migrationSkill
- write-reportSkill
- write-testSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 181 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 144
No relatorio final (Passo 6), substitua a secao Reviews por:
“Common” is measured: kept by at least 6 in 10 of the 181 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Voce deve entregar a branch atual como PR no GitHub. Execute todos os passos em ordem. Pare e reporte ao operador se qualquer verificacao ou comando falhar.
Passo 0 -- Verificacoes de seguranca (ADR-011)
Execute cada verificacao via Bash (PowerShell). Se qualquer uma falhar: reporte exatamente qual falhou e termine sem fazer push ou PR.
V1 -- branch nao e main:
$branch = git branch --show-current
if ($branch -eq "main") {
Write-Host "ERRO: voce esta em main. /ship opera apenas em branches de feature."
exit 1
}
Write-Host "Branch: $branch"V2 -- working tree limpa:
$status = git status --porcelain
if ($status) {
Write-Host "ERRO: working tree nao esta limpa. Commite ou descarte as mudancas antes de /ship."
Write-Host $status
exit 1
}
Write-Host "Working tree: limpa"V3 -- ha commits acima de main:
$ahead = git rev-list --count main..HEAD
if ($ahead -eq 0) {
Write-Host "ERRO: nenhum commit acima de main. Nao ha nada para shipar."
exit 1
}
Write-Host "Commits acima de main: $ahead"V4 -- gh CLI disponivel e autenticado:
gh auth status 2>&1 | Out-Null
if ($LASTEXITCODE -ne 0) {
Write-Host "ERRO: gh CLI nao autenticado. Rode 'gh auth login' antes de /ship."
exit 1
}
Write-Host "gh CLI: autenticado"Passo 1 -- Gate completo
.\scripts\check.ps1Se exit code != 0: escreva "ERRO: gate falhou (check.ps1 exit $LASTEXITCODE). Corrija antes de shipar." e termine. Nao faca push.
ATENCAO: check.ps1 exige Docker Desktop rodando (Testcontainers). Se Docker nao estiver ativo, o gate falhara na verificacao de Docker antes de qualquer teste.
Passo 1.1 -- Gate frontend (condicional)
Verifique se ha arquivos em frontend/ entre os commits da branch:
$frontendChanged = git diff --name-only main..HEAD | Where-Object { $_ -like "frontend/*" }Se $frontendChanged for nao-nulo e nao-vazio: execute o gate frontend:
# Garantir que estamos na raiz do repositorio (executor pode ter feito cd em subdir)
Set-Location (git rev-parse --show-toplevel)
.\scripts\check-front.ps1Se exit code != 0: escreva "ERRO: gate frontend falhou (check-front.ps1 exit $LASTEXITCODE). Corrija antes de shipar." e termine. Nao faca push.
Se $frontendChanged for nulo ou vazio: pule este passo (sem arquivos frontend
na branch, gate nao se aplica).
Passo 2 -- Push
$branch = git branch --show-current
git push -u origin $branchSe exit code != 0: escreva "ERRO: push falhou." com o output do git e termine. Nao crie PR.
Passo 3 -- Extrair informacoes para o PR
$titulo = git log -1 --format="%s"
$commits = git log main..HEAD --oneline
$branch = git branch --show-currentPasso 4 -- Criar PR
Monte o body do PR com a lista de commits e o aviso padrao. Execute:
gh pr create `
--title $titulo `
--base main `
--body "## Commits nesta branch
$commits
---
_Gerado via /ship. Adicione detalhes de decisao e smoke se necessario._"Se exit code != 0: escreva "ERRO: gh pr create falhou." com o output e termine.
Passo 5 -- Reviews automaticas
Extraia o numero do PR da URL retornada pelo gh pr create (ultimo segmento da URL).
DETECCAO DE CONTEXTO (executar antes de qualquer review):
Verifique se voce esta num worktree isolado (sub-agente de /batch ou /plan):
if [ -f .git ]; then
echo "WORKTREE: Agent tool indisponivel -- pular reviews automaticos"
else
echo "REPO_PRINCIPAL: Agent tool disponivel -- executar reviews"
fiSe .git for um ARQUIVO (worktree): pule os Reviews 1, 2 e 3 inteiramente.
No relatorio final (Passo 6), substitua a secao Reviews por:
Reviews:
PENDENTE -- executor rodou em worktree (Agent tool indisponivel).
Rodar manualmente antes do merge:
/review-pr <numero>
/review-front <numero> (se houver mudancas em frontend/)Se .git for um DIRETORIO (repo principal): prosseguir normalmente com os reviews abaixo.
Verifique se ha arquivos em frontend/ entre os commits da branch:
$frontendChanged = git diff --name-only main..HEAD | Where-Object { $_ -like "frontend/*" }Emita TODOS os reviews aplicaveis em UMA UNICA resposta (acao atomica -- nao sequencial):
- Sempre: Agent call para
pr-reviewercom promptRevise o PR #<numero> do repositorio financas-lab antes do merge. - Sempre: Agent call para
architect-reviewercom promptRevise as decisoes arquiteturais do PR #<numero> do repositorio financas-lab contra os ADRs do projeto. - Se
$frontendChangednao-vazio: Agent call parafront-reviewercom promptRevise as mudancas de frontend do PR #<numero> do repositorio financas-lab.
Aguarde TODOS os reviews terminarem antes de processar os resultados. Se qualquer review reportar bloqueador: inclua no relatorio final e sinalize ao operador. Nao cancele o /ship -- o PR ja foi aberto.
Passo 5.1 -- Correcao autonoma de apontamentos
Regra 1 — O que corrigir (filtro obrigatorio)
Corrija APENAS apontamentos classificados como Bloqueador (## Bloqueadores)
nos outputs dos reviews. Nunca corrija apontamentos de ## Sugestoes nem de
## Elogios.
Exemplos de IDs de bloqueadores: B1, B2, B3, ..., B13 (front-reviewer), violacao de ADR (architect-reviewer), logica incorreta (pr-reviewer).
Se todos os apontamentos forem Sugestoes ou Elogios: pule este passo inteiramente e va direto ao Passo 6.
Regra 2 — Apontamento subjetivo vs. objetivo
- Objetivo (corrija autonomamente): falta de anotacao, import ausente,
variavel nao usada, violacao clara de convencao ADR estabelecida,
text-rightausente em celula monetaria,asChildem base-nova, fetch direto fora de services/. - Subjetivo (reporte e aguarde): redesign de interface, mudanca de estrategia, decisao que afeta outros bounded contexts.
Regra 3 — Protocolo de edicao (obrigatorio, sem excecao)
Para cada bloqueador objetivo a corrigir, executar nesta ordem exata:
Passo A — Ler o arquivo completo antes de qualquer edicao:
Read(<path-do-arquivo-apontado>)Nao editar sem antes ter lido o arquivo na integra. Sem excecao.
Passo B — Aplicar o fix minimo em UMA unica operacao Edit:
- Uma chamada de Edit por apontamento.
- Se o fix exigir mais de uma edicao no mesmo arquivo: fazer tudo numa unica chamada Edit com o bloco completo de mudanca.
- Se apos a edicao perceber que ficou errado: reportar como BLOQUEADOR para o operador. NAO tentar editar de novo em loop.
Passo C — Validacao pontual (nao o gate completo):
- Fix em arquivo
.tsxou.tsfrontend:
Se nao houver arquivo de teste para o arquivo corrigido: pular validacao.cd <worktree>/frontend && npm run test:run -- <path/do/arquivo.test.tsx> - Fix em arquivo
.java:
Se nao houver teste correspondente: pular validacao../mvnw test -Dtest=<ClasseTest> -q - Fix em arquivo
.ps1,.sql,.ymlou doc: sem validacao automatica.
Passo D — Proibicoes absolutas:
- NUNCA criar arquivos de teste temporarios ou probe (
__probe.*,*_temp.*, qualquer arquivo que sera deletado em seguida). - NUNCA rodar
check.ps1oucheck-front.ps1por fix individual. - NUNCA rodar
npm run test:runsem filtro de arquivo especifico. - NUNCA editar o mesmo arquivo mais de uma vez por apontamento.
Regra 4 — Gate final unico
Apos aplicar TODOS os fixes (nao apos cada um individualmente):
.\scripts\check.ps1Se houver mudancas em frontend/:
powershell -NoProfile -Command "Set-Location (git rev-parse --show-toplevel); .\scripts\check-front.ps1"Se qualquer gate falhar: reportar o erro ao operador. NAO tentar corrigir automaticamente apos falha de gate — esse ciclo e irrecuperavel autonomamente.
Regra 5 — Commit e push
Apos gate final passar:
git add -A
git commit -m "fix(<scope>): <lista dos apontamentos corrigidos separados por virgula>"
git pushEditar o body do PR adicionando secao ## Correcoes autonomas:
gh pr edit <numero> --body-file <arquivo-com-body-atualizado>Listar cada apontamento corrigido com: ID, arquivo, descricao da correcao.
Se nenhum bloqueador objetivo existir: pule este passo e va direto ao Passo 6.
Passo 6 -- Relatorio final
Produza:
/ship concluido.
Branch: <branch>
Gate: check.ps1 passou
Push: OK
PR: <URL retornada pelo gh pr create>
Titulo: <titulo>
Commits: <numero> acima de main
Reviews:
pr-reviewer: <OK / BLOQUEADOR: <motivo>>
architect-reviewer: <OK / BLOQUEADOR: <motivo>>
front-reviewer: <OK / BLOQUEADOR: <motivo> / N/A (sem frontend)>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

