The Web Guy AI Code Review
Review a specific change before merge or launch.
Have a branch, pull request, generated feature, or AI-built site ready for another set of eyes? I review the change in context and explain what should be fixed, tested, or clarified before you merge or launch.
Free quote. Engineering work starts after scope and cost are agreed.
Inside a review
Automated checks and AI review can catch useful issues. Human review adds the questions that depend on understanding the application and the original requirement. I look at the diff, the surrounding code, and the behavior it is supposed to change.
export const service = {path: '/old-service/'path: '/new-service/' 1};The changed line is visible. Its dependencies need a closer look.
Agree the boundaries
We choose the review areas that fit your change. A focused pull request review and a whole-site launch review are different scopes.
A focused pull request is a useful starting point. Broader access or scope is discussed before the work expands.
Duplicated logic, component reuse, data ownership, configuration, error handling, and maintenance cost.
Changed routes, forms, APIs, shared components, and the existing flows that depend on them.
Authentication, authorization, input validation, secret handling, and dependency risks within the agreed scope. This is not a penetration test or a security certification.
URLs, redirects, canonicals, metadata, structured data, internal links, sitemaps, and conversion events.
Extra requests, script weight, rendering, layout shift, keyboard access, labels, focus, and semantics.
Build output, environment assumptions, runtime behavior, deployment steps, and the checks needed after release.
Your handoff
Findings connect the affected area to an action, a decision, and the checks still needed.
Illustrative finding / 01
Example format, not a client finding. Actual findings depend on the agreed review.
Tell me what exists, what you need checked, and your next deadline. I will confirm fit, scope, and cost. No repository URL required.
Before we start
The quote is free. Hands-on engineering is paid work within an agreed scope.
Yes. A bounded diff is often the best starting point. If a change depends on shared code, configuration, or an existing flow, I may need that context too. Any expansion of scope is discussed first.
Yes. Describe the work in the quote request. We can arrange the minimum repository access needed after agreeing scope. Keep private repositories private and do not send credentials through the form.
That is a useful starting point. Review checks whether it fits the application, preserves other behavior, and leaves a maintainable implementation. It may confirm the approach or identify changes before release.
Only when they are part of the agreed scope. The quote can cover review alone or review plus fixes, refactoring, and verification. You decide before paid work starts.
The quote is free. Code review, testing, diagnostics, and implementation are paid services. I confirm scope and cost before beginning.
Yes. Reviews can cover PHP, themes, plugins, JavaScript, CSS, and how the change interacts with the existing WordPress site.