メニュー
Undo the last AI change without losing user work. Use when the latest AI-applied change broke something, the user says "desfaz", "volta", "undo", "estraga tudo", or after `bug-triage-agent` selects a revert as the safest fix. Designed for vibe coders who don't yet trust git.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Plan post-first-100-users growth without burning out the founder, the budget, or the user base. Pairs with `first-100-users` (which gets you to 100); this skill takes you from 100 to ~1000 sustainably. Activated when the user says "já tenho 100 usuários, e agora?", "como cresço sem queimar dinheiro?", "o WhatsApp 1-a-1 não escala mais".
Get a second (and third) AI opinion on hard-to-reverse decisions. Runs the same prompt through different agent roles or model families in parallel, then reconciles disagreements. Inspired by gstack's `/codex` cross-review pattern. Activated for architecture decisions, security-sensitive code, pricing/packaging changes, deploy gates, legal-adjacent text, or any decision the user flags as "não dá pra desfazer fácil".
Turn a manually-validated workflow into a documented, repeatable, and partially-automatable process. Use AFTER a task has been done at least 3 times by hand and is showing signs of repetition. Inspired by Sahil Lavingia's principle "do it manually until it works, then processize." Activated when the user says "tô fazendo isso toda semana", "vamos automatizar?", "isso já cansou", or after `daily-standup` flags repeated manual work.
Recommend external repo packs from docs/registry/ that fit a project's stack, domain, and constraints. Use during /project-start (after the Technical Plan), when the user asks "que repos eu deveria usar?", or whenever a new need (security review, design system, deploy guidance) appears mid-build.
Flag potentially expensive technical choices BEFORE they are committed. Watch for AI model selection, hosting tier upgrades, third-party services with metered pricing, and DB patterns that explode with scale.
At the start of a session (or on user request "o que a gente fez", "onde paramos"), produce a 4-bullet briefing — what's done, what's in progress, what's next, what's blocked. Replaces the dev habit of standup for solo vibe coders.
| name | rollback-safe |
| description | Undo the last AI change without losing user work. Use when the latest AI-applied change broke something, the user says "desfaz", "volta", "undo", "estraga tudo", or after `bug-triage-agent` selects a revert as the safest fix. Designed for vibe coders who don't yet trust git. |
bug-triage-agent recommends a revert.Pensa numa máquina do tempo do projeto. Cada commit é uma foto do projeto inteiro. "Desfazer" não apaga a foto — ele só te leva pra foto de antes. Se mudar de ideia, você pode voltar pra foto atual a qualquer momento. Nada que você fez se perde.
Use git restore <file> for unstaged changes, git restore --staged <file> for staged.
Safe and instant.
git revert HEAD --no-edit
Creates a new commit that undoes the previous one. History stays linear, nothing lost.
Pick the last good commit hash and:
git revert <bad-commit>..<HEAD> --no-edit
Each bad commit gets its own undo commit.
Use git revert (not git reset --hard) so collaborators / CI / Vercel pick up the undo cleanly.
git reset --hard <hash> rewrites local history. Only use after explicitly asking the user, AND backing up untracked files first. Never on a shared branch.
Before running ANY rollback command:
Snapshot uncommitted work.
git stash push -u -m "rollback-safe-snapshot-$(date +%s)"
Even if it looks like "nothing important", stash it. Stashes can be popped back.
Confirm the target. Show the user the exact commit (hash, message, date) you're about to undo.
Show the blast radius. List which files will change.
Confirm with the user in plain Portuguese.
Vou voltar o projeto pro estado antes de [commit msg].
Isso vai mudar [N] arquivos.
Seu trabalho não-commitado tá guardado e dá pra voltar.
Posso prosseguir?
Apply.
Verify build still works (use verify-build-works).
git log --oneline -5).session-log/ explaining why we rolled back.git reset --hard HEAD~1 without snapshot.git push --force to "clean up" remote history on a shared branch.↩️ Rollback safe report
Snapshot: stash@{0} (rollback-safe-snapshot-1714329600) — seu rascunho tá aqui se precisar.
Voltei o projeto pra: 7604d32 ("docs: prepare public release metadata")
Arquivos afetados: 11
Build: ✅ ainda passa
Próximo passo: testar o fluxo que estava quebrando.
Se quiser desfazer esse desfazer: me pede "rebobina o rebobina".