Apply Fix & GitHub
How Apply Fix works
The end-to-end flow from clicking Apply Fix to a merged PR on your repo.
4 min read
Apply Fix is the feature that opens a GitHub Pull Request with the change pre-written for you. Here's what happens when you click it.
Step 1: detect the source file
We use the affected URL to find the source file in your repo. For a page at /login.html, we look for public/login.html, login.html, or the Next.js equivalent app/login/page.tsx. We pick the most likely match and pre-fill the “File to edit” field.
Step 2: generate the fix
Claude reads the current file content and the issue context, then either:
- For common SEO tags (meta description, title, canonical, robots, og:image, JSON-LD): a deterministic regex patch swaps the tag. Fast and precise.
- For complex changes: Claude rewrites the relevant portion of the file with the fix integrated.
Step 3: open the PR
- We create a new branch like
semantyx/fix-meta-description-XXX. - We commit the change to that branch.
- We open a PR against your base branch (typically
main) with a detailed PR description. - You get the PR URL in the dialog. Click through, review, merge.
Safeguards
- If Claude returns the file unchanged, we abort (probably wrong file picked).
- If the merged file is wildly larger/smaller than the original, we abort (something went wrong).
- If the file is over 256KB (probably a generated bundle), we abort and ask you to point at the source.
- We never auto-merge. Every PR waits for a human to click merge.