Writing code
Connect GitHub and name the repository. State the problem, required behavior, and the checks to run.
In
acme/web, make the invoice table sortable by due date. Preserve the current mobile layout. Add the test that proves the sort order, run the focused checks, and open a pull request. Do not merge it.
Define the change
Section titled “Define the change”State:
- The repository and base branch.
- The behavior that must change.
- Constraints, affected environments, and files that must not change.
- The tests or manual checks required.
- Whether your UFO may commit, push, open a pull request, or merge.
Your UFO reads repository instructions before it changes code. If the repository contains
AGENTS.md, those instructions apply to files in its scope.
Follow the work
Section titled “Follow the work”The final reply includes the change, test results, and pull request. Check CI and merge status separately; local tests do not show whether CI passed or the pull request merged.
Ask your UFO to keep watching when the required outcome includes CI or review:
Watch this pull request until all required checks and reviews finish. Fix failures caused by this branch. Do not merge it.
Review the result
Section titled “Review the result”Review the code changes and check how the product works. For a visual change, ask UFO to check the page in a browser at desktop and phone widths. For a data change, check that realistic data is saved correctly and appears where users need it.
See the complete code change recipe.