Reviewed · Published by RiverX
Start with a change you can verify
Write the desired behavior, files likely to be involved and the tests that should remain green. A useful first task is adding a validated form or repairing a reproducible bug. Keep the change small enough to review as a diff. Treat the generated implementation as code you are responsible for maintaining.
Choose a runtime and a model deliberately
RiverX supports Codex and OpenCode coding-agent runtimes, with availability depending on configuration, and exposes selectable catalog models. Check tool support, modalities and context for the task. Skills can supply recurring project instructions; review those instructions before applying them and keep project-specific rules in the brief.
Review behavior at the boundaries
Inspect how the change handles an invalid request, a missing record, a failed service and a user without permission. Run the project's tests and use preview for interactive behavior. If a new dependency is added, check why it is needed and how it affects the build. A plausible implementation or a passing screenshot does not establish correctness.
Use source control as the review surface
Push the workspace source through the authenticated GitHub workflow and review the intended branch. Pull requests provide a separate place to inspect and discuss proposed code before merging. Verify how your local changes return to RiverX; this page does not promise automatic two-way synchronization or CI orchestration.
Sources: GitHub pull request guidance
Own the release and the operating cost
Check generated environment configuration and the provisioned database before publishing. Repeat the acceptance test at the live URL and record actual metered usage, including retries. For a larger project, establish a budget and a maintenance owner. RiverX assists implementation; architecture, security and release decisions still need engineering judgment.
Start with a real project
Explore published templates, then make the application your own.
Which coding agents does RiverX support?
The implementation includes Codex and OpenCode runtimes. The available choice depends on runtime configuration; inspect the actual product before planning around a specific combination.
Can RiverX replace code review?
No. Review diffs, dependencies and sensitive code paths, run tests and inspect the deployed behavior before accepting a change.
What is a good first developer task?
Use a focused change with a reproducible starting point and explicit acceptance criteria, such as form validation or a small bug fix. That lets you evaluate quality and actual usage cost.
Does every generated project support my existing CI setup?
No universal compatibility is established. Inspect the generated framework, dependency lockfile, test commands and environment requirements in your CI environment.
Put the pieces together
Models, instructions and starting points for your next project.