Turn a website change into a reviewable update.
Claude Code | Delegated coding · reviewed before release
https://automately.cc/automate/claude-code-website-update

Give Claude Code a bounded change in an existing project. Let it find the files, implement the update, and run the relevant checks before you decide to release it.

ACCESS
Use Claude Code with access to a project you are authorized to edit. Follow its official setup guide for your preferred environment. You need the project's normal preview and test commands.

BEFORE YOU START
A project backup or a clean Git branch
One page and one clear change
Acceptance criteria and the normal checks

1. Open the project and define the change
Use a clean branch or project copy. Open Claude Code in the project. Write down the page, the element, its desired behavior, and what a successful result looks like.
Check: You can explain the change in one sentence and undo it.

2. Let Claude find and edit the right file
Send the prompt. Ask it to follow repository instructions and preserve unrelated work. If it finds several matching buttons, identify the correct one before it edits.
Check: The proposed files match the requested page.

3. Review the diff and the page
Inspect the actual changed lines. Open the normal project preview and check desktop and mobile sizes. Click the CTA in a safe preview to confirm its destination. Read the test results and any stated limitations.
Check: Only the intended behavior changed and the evidence supports that.

4. Decide whether it is ready to release
Use your project's normal review and deployment process after the checks pass. For a repeated maintenance job, save a written checklist or a Claude Code skill. A saved skill alone is not a schedule.
Check: The release follows your existing project process.

PRACTICE INPUT
Practice change brief
Page: contact page.
Button: change Get started to Book a call.
Destination: keep the existing booking URL.
Check: desktop and mobile layout.

PROMPT
Inspect this repository and its project instructions. On the contact page, change the primary CTA label from Get started to Book a call. Preserve the existing destination and other content. Locate the relevant component, implement the smallest change, and run the project's relevant checks. Show the changed files, a summary of the diff, and any check you could not run. Do not commit, push, deploy, change dependencies, or edit environment files. Ask if the page or button is ambiguous.

ILLUSTRATIVE RESULT
Proposed change
Contact CTA: Get started → Book a call
Destination: unchanged
Evidence: changed file and diff
Checks: actual results, with any gaps
Release: waiting for your decision

REPEAT
For the next small website change, follow the same process: inspect project instructions, identify the smallest edit, preserve unrelated work, run relevant checks, and return a reviewable diff. The new change is [specific request]. Stop before commit, push, or deployment.

FALLBACK
If you do not have repository access, ask Claude or ChatGPT to prepare a precise change brief for your developer. A text suggestion has not changed the live website.

CHECKLIST
Changed files match the requested scope
Links and mobile layout checked
Actual test results reported accurately
Deployment is a separate, intentional step

Sources reviewed October 31, 2026. Original recipe; not account-tested.
Claude Code: common workflows: https://code.claude.com/docs/en/common-workflows
Claude Code: setup: https://code.claude.com/docs/en/quickstart