Module 04 of 18 · Build

Code and repo

Everything Neo builds is a real project in a git repository you own: Swift, Next.js, Godot, Unity or Unreal. The team searches the code, runs the tests, reviews its own changes and writes the changelog. When a build fails it fixes it itself, up to eight passes, and what went wrong becomes a rule the team checks next time.

You say
“Run the tests and fix what fails.”
Neo · Code and repo
The team is working
0/5
Searched the code for the change
Tests run
Automated code review
Changelog written
Committed to your repository

A recreated panel in the style of the app: how a turn in this module goes, built only from what the module really does.

What you can do with it

5 things you can do with it.

SwiftNext.jsGodotUnityUnreal

A repository you own

Every project is a real codebase on your computer, under git.

Build
Tests
Fix
Build again

Tests and self repair

Failed builds are fixed by the team, up to eight passes, before you see them.

Review this change before we ship it.

Code review

The team reviews its own changes before they reach you.

BranchCommitPushPR

GitHub

Branches, pushes and pull requests, with your approval for anything outward.

> neo build "A mental wellness app…"

From the terminal

Every module is also a command in the Go CLI, with JSON output for scripts and CI.

You say…

Plain words in the one chat.

“Run the tests and fix what fails.”
“Review this change before we ship it.”
“Write a changelog for this version.”

You never pick the module. Neo reads the request, picks Code and repo, and says why.

What you get at the end

What you hold when it is done.

  • A build that opens and passes its tests
  • A log of what broke and how it was fixed
  • Commits in a repository you own

Anything that spends money, publishes or deletes stops and asks you first, with the price on the button.