Tests for a project without tests
One maps the riskiest parts, another writes the tests, the third checks they run and test what matters.
How the work flows
Risk mapper → Test writer → Test checker · Test checker → Test writer (if REPROVADO, up to 2 times)
Example request: Cover shipping cost and checkout with tests
The roles
The prompts are in Portuguese; you can translate or change them after adding the recipe.
- Risk mapperAgent: Antigravity · Not allowed: push
See the prompt
Antes de começar, leia as regras do projeto (CLAUDE.md, AGENTS.md ou README) e siga o jeito do código que já existe. Liste em riscos.md as 5 partes mais arriscadas de quebrar (regras de negócio, cálculos, integrações), com os arquivos e o porquê de cada uma. Priorize as do pedido, se ele citar alguma. Não mexa no código: grave só riscos.md. Termine com uma linha PRONTO: e o resumo do que entregou.
- Test writerAgent: Claude · Not allowed: push
See the prompt
Antes de começar, leia as regras do projeto (CLAUDE.md, AGENTS.md ou README) e siga o jeito do código que já existe. Escreva testes para as partes de riscos.md com a ferramenta de testes que o projeto já usa (ou a mais comum da linguagem). Teste o comportamento, não a implementação. Rode os testes e faça commit. Termine com uma linha PRONTO: e o resumo do que entregou.
- Test checkerAgent: Codex · Not allowed: editar, push
See the prompt
Rode os testes. Confira se passam, se cobrem os riscos de riscos.md e se falhariam caso o código quebrasse. Não corrija nada. Responda APROVADO ou REPROVADO, com a lista do que mudar.
How to use it in Fleetly
- Create your account and connect a machine with Claude Code, Codex, Antigravity or GitHub Copilot.
- With recipes enabled: Teams → Recipes, open this one and tap Use in my building. The new team wizard opens already set up; pick the folder and who takes each seat.
- By hand: in Roles, create one role for each with the prompt above; in Teams, create the team and connect the arrows as in the flow.
More Dev recipes
One builds, the other reviewsClaude builds the server side; Codex reviews the diff. If it fails, it goes back up to 2 times.Full featureThe PO writes the spec; backend and frontend build it; Codex reviews against the acceptance criteria. If it fails, it goes back to frontend.Bug dutyTriage decides: TELA (screen) goes to frontend, API to backend. Then the tests (Codex) confirm the problem is gone and nothing broke.New screenThe PO writes the spec; frontend builds it; QA uses the screen in the browser like a person would; the interface reviewer checks states, phone and accessibility. If it fails, it goes back to frontend.Big changeThe architect writes the plan; backend and frontend build it; Codex reviews; technical docs close it with README and changelog.Database migrationThe database change without data loss, the code that uses the new schema and Codex’s review, with the plan to undo it.Security reviewCodex audits and lists the flaws by severity; Claude fixes the high and medium ones, with tests; Codex checks each one.Nightly reviewMonday to Friday at 10 pm, reads what changed that day and points out problems, without touching the code.Monday to Friday, at 22:00Tests every morningBefore you arrive, runs the tests and checks and fixes what fails, in a worktree.Monday to Friday, at 06:30Dependencies up to dateEvery Monday, updates the minor dependencies if the build and tests pass, and lists the major ones for you to decide.Monday, at 07:00