# Building Safely: 3 prompts for when you build for real

These are for AFTER the workshop, when you go build something real and want a safety net. They make Claude own the Git, branch, check, and review process for you, so a non-technical builder does not break things or ship something unsafe. They degrade gracefully: if you do not have CodeRabbit or Greptile set up, Claude just skips that step.

Use them in order: start a build safely, review before merge, fix the findings.

## 1. Start a new build safely

You are my coding agent. I am not technical, so you own the Git/branch/PR/check process.

Before editing, inspect the repo and tell me:
1. What branch we are on
2. Whether it is safe to work here
3. What branch you will use
4. What checks exist

Then implement the requested change on a feature branch, run the available checks, run CodeRabbit or Greptile review if available, fix meaningful findings, and end with:

Safe to merge/deploy: Yes/No/Not enough evidence
Evidence: branch, PR, checks, review, smoke test
Remaining risk:
What I need from you:

Task:
[describe what you want built]

## 2. Review before merge

Please do a pre-merge safety review for me. I am not technical.

Check the current branch/PR, run available lint/typecheck/test/build commands, run CodeRabbit or Greptile if available, and inspect the diff for correctness, security, data-loss, auth/payment, dependency, and deployment risks.

Do not merge. Do not deploy.

End with:
Safe to merge: Yes/No/Not enough evidence
Blocking issues:
Non-blocking issues:
Evidence:
Recommended next action:

## 3. Fix review findings

Please fix the meaningful code review findings. Ignore style nitpicks unless they point to real bugs or maintainability risk.

Prioritize:
1. broken build/test/typecheck
2. runtime crashes
3. auth/payment/security issues
4. data loss or database risk
5. user-visible regressions
6. missing tests for risky logic

After fixes, rerun the relevant checks and tell me whether it is safe to merge.

## Where these fit on Day 4 (instructor note)

These are a take-home / level-up resource, not a core step in the live scaffold build. The live build is from-scratch and fast, and a full PR plus CodeRabbit/Greptile review is the discipline you add once you are iterating on a real repo, not while scaffolding a v1. CodeRabbit and Greptile are optional code-review tools; the "if available" wording means the prompts still work without them.

The one piece worth doing live is the spirit of prompt 1: have Claude set up Git so you can roll back (the same move several beginner tutorials make). The rest is for Monday, when members build for real.