Apply changes.

> /finch-apply

What it does

1. Picks up your queued changes. The page shows “Claude is applying…”.
2. Makes a branch from your main branch, named like finch/apply-1a2b3c4d.
3. Makes each change the way your project already styles things, and commits each one on its own. Each change ticks off on the page as it lands.
4. Checks the build. If a change breaks it and can’t be fixed, that change is left out.
5. Checks which files changed. If anything touched package files, build or deploy settings, environment files or CI, it stops and asks you before going on.
6. Merges into main and deploys: ample up, vercel --prod for linked Vercel projects, or a git push when your host deploys on push. Otherwise it asks once how your site deploys and remembers it.
7. Reports back. Each change is marked done, or reopened with a note, and the page reloads into the live version.

When a change can’t be applied

• Conflict: the code no longer has the value the change started from (someone changed it since). Claude leaves it alone and says what the code has now; the suggestion goes back on your page.
• Skipped: a note that was a question, out of scope, or unclear about what to change.

Undoing a change

Every change is its own commit, and the branch is kept, so you can ask Claude to revert any one change without touching the others.

Safety

What reviewers type is treated as feedback, never as instructions to Claude. For image changes, Claude picks only free photos from Unsplash or Pexels and tells you which one it chose.