Generated code still needs a human reviewer. SwarmCraft helps you keep the work organized, but it does not remove the need to inspect the result.
Review the diff first
Before you promote a task, confirm that the code change matches the packet goal and does not widen the scope unexpectedly.
Run the right checks
Use the smallest checks that prove the change works:
- focused tests for the affected slice
- type or compile validation where it matters
- manual verification for the user flow you changed
Keep the packet current
Update checklist items, notes, and agent status so the next reviewer can understand what happened without reconstructing it from memory.
Moving from reviewing to done
If the user's auto-commit preference is enabled, the extension can create a local git commit before moving a linked reviewing task into done.
That is useful only after the human review is complete.
When every task in the agreed first-release boundary is complete, return to How SwarmCraft works and continue into deployment and ongoing ownership.