Code Readiness checks
Before your app goes online, it helps to have a few small things in place — a way for the system to check the app is alive, a recipe for packaging it up, automatic build steps. The Code Readiness step handles all of that for you. An AI helper called the Code Doctor looks over your code and suggests tidy, safe improvements that make deployment smooth and reliable.
What the Code Doctor does
When you open the Code Readiness tab, the Code Doctor reads your repository and looks for anything missing for a dependable deployment. It then proposes a short list of small, self-contained changes. Common examples:
| Suggestion | Why it helps (in plain terms) |
|---|---|
| Health check | Adds a simple "am I alive?" endpoint the system can ping to confirm your app is running |
| Containerization (Dockerfile) | A Dockerfile is a recipe for packaging your app so it runs the same everywhere |
| CI/CD config | Sets up automatic build-and-ship steps so future updates deploy cleanly |
| Build hygiene / configuration | Small housekeeping files that make builds faster and cleaner |
If your repo already has everything it needs, the Code Doctor will simply say there's nothing to change — that's a good sign.
Reviewing each suggestion
Every suggestion is shown as its own card, and each one is independent — you're always in control:
- Read the title, the rationale (why it's suggested), and the benefit (what you gain).
- Click the file path to preview the exact file that would be added or changed. Each card is tagged new file (create) or modified, so you know whether it's adding something or adjusting an existing file.
- Uncheck anything you don't want. Leave the checkbox ticked to include it.
Applying = a commit to your branch
When you're happy, click Review & commit. You'll get one more chance to edit any file before anything is saved. Then confirm, and all your selected changes are committed to your repository on the branch you chose, in a single tidy commit. That means the improvements become a real part of your code — you can see them in GitHub afterwards.
Prefer not to change anything? Click Skip — deploy as-is and move straight on. You can always come back and run the Code Doctor again later with Re-analyze.
Why it's safe
- Small and atomic. Each change is minimal and independent, so nothing sweeping happens by surprise.
- You review everything. No file is committed until you've seen it, optionally edited it, and confirmed.
- It's your branch. Changes go to the exact branch you picked when creating the project — the app never touches other branches.
- Checked before commit. The generated code is validated so it won't break your build, and if anything ever does slip through during launch, the Recovery Agent can repair it automatically.
Once you've applied the changes you want (or skipped), continue to choosing an architecture.