Make the change and test it on Dev
Everything here happens in your branch and the develop branch. Nothing touches Production.
-
1
Create your branch from the
developbranch You + ClaudeYour branch is your own workspace for one change. It must be copied from the
developbranch, not themainbranch.Tell ClaudePull the latest develop branch and create a new branch off of the develop branch for [describe your change].
-
2
Make your changes in your branch You + Claude
Work with Claude as usual. Test your changes at
http://localhost:5173. When they work, have Claude save and push your branch.Tell ClaudeCommit these changes with a clear message and push my branch.
-
3
Open a Pull Request into the
developbranch You + ClaudeA Pull Request (PR) asks the AI App Review group to review your branch and allow it into the
developbranch. It must point at thedevelopbranch. Include a short test summary.Tell ClaudeOpen a pull request from my branch into the develop branch. Summarize what changed and how I tested it.
-
4
AI App Review approves, then you merge AI App Review You + Claude
The review group looks over the PR and may ask for tweaks. Once they approve it, the merge is up to you — merge whenever you’re ready for the change to go to the Dev site.
Tell Claude (after approval)My pull request into the develop branch has been approved — merge it.
-
5
Dev updates itself Automatic
Within a few minutes of the merge, your change is live on the Dev site. No action needed.
-
6
Test your changes on the Dev site You
Open the Dev site and test your changes the way a real user would. Something off? Go back to step 1 and create a new branch to fix it.