Connect a Shopify theme to Git and an AI coding agent

What connects to what

Three things join up, and each keeps its own job. Git is the source of truth for the theme’s files. Shopify renders those files as the storefront and owns the data—products, prices, inventory, customers. An AI coding agent such as Claude Code or Codex reads and edits the repository the way a developer would. The mistake most stores make is skipping the middle layer entirely: editing Liquid in the admin code editor, on the live theme, with no history and no review. That is the habit this workflow removes.

Shopify’s GitHub integration is the join. You connect a theme to a repository and branch, and from then on the branch and the theme stay equal: commits to the branch update the theme in the admin, and edits saved in the admin are committed back to the branch. A theme connected this way shows its repository, branch and last commit time on the theme card, and if it drifts you can pull the branch back with Actions → Reset to last commit. A published theme connected to a branch updates the live storefront when commits land on it. Shopify: GitHub integration for themes

Locally, the Shopify CLI gives the agent the same tools a person uses: shopify theme dev starts a hot-reloading local preview against a real store, shopify theme check lints the Liquid and theme structure, andshopify theme pull/push move files to and from an unpublished theme. None of that needs Shopify Plus, and it applies whether you started from Dawn or built every section from scratch. Shopify: CLI for themes

The two-way loop, drawn out

The important detail is that preview and live are two different themes. Feature work runs on an unpublished theme connected to a feature branch; the merchant, a reviewer or a client can open its preview URL and see the change against real products and prices without any risk to the storefront. Only when the pull request is reviewed and merged into the branch the published theme mirrors does the change reach shoppers—and because that is a single commit, undoing it is a single revert. This is what lets the agent move quickly: fast is safe when every step is isolated and reversible.

How Appycodes uses this for UK & EU stores

We run this workflow for UK and EU Shopify merchants across very different catalogues. Two anonymised examples show the range—both are custom engineering on Shopify, kept in Git, worked through previews and reviewed pull requests rather than the admin code editor.

The Git-to-Ship Score

Before we let anyone—person or agent—move fast on a theme, we check five gates. Score each 0 when absent, 1 when partly there, 2 when configured, and 3 when proven on a real change. This is operational readiness, not a Shopify certification: a store can be live and still score badly here, which is exactly when a “quick fix” becomes an outage.

Grounding the agent

The difference between an agent that helps and one that creates cleanup is almost entirely context. A short conventions file—CLAUDE.md for Claude Code, AGENTS.md for Codex—teaches it the repository the way you would brief a new developer: the stack, the brand tokens, the files it must not rewrite, and the branch → preview → check → review loop it has to follow.

# CLAUDE.md  (Codex reads AGENTS.md — keep one file, symlink the other)
# The repository conventions the agent must follow. This is what turns a
# generic model into an engineer who edits like the rest of the team.

## Never
- Edit the live theme in the Shopify admin code editor.
- Rewrite config/settings_data.json — it holds the merchant's own
  customiser choices. Flag any change to it in the PR instead.
- Hard-code brand colours or fonts. Tokens live in assets/brand.css.

## Stack
- Dawn-based Online Store 2.0 theme: sections + JSON templates, so every
  page stays editable in the customiser after we ship.
- Product / Offer / BreadcrumbList JSON-LD lives in snippets/*. Keep it valid.

## Every change
- New branch. `shopify theme dev` to preview against the store.
- `shopify theme check` must pass before you commit.
- Open a pull request. A human reads the diff before it reaches main.

One pipeline, four kinds of change

The point of a version-controlled theme is that every kind of change uses the same road. A new section, a checkout bug fix, an SEO title rewrite and a GEO structured-data improvement all enter as a branch, get a preview, pass Theme Check, get read by a human, and merge as one commit. There is no separate, riskier path for “small” SEO edits made directly in the admin—the class of change that quietly breaks canonical tags or JSON-LD on a Friday afternoon.

Continuous integration is what makes review affordable at speed. A single GitHub Actions workflow runs Theme Check on every pull request, so Liquid errors, deprecated filters and accessibility problems fail the merge instead of reaching the store. It needs no store credentials, because Theme Check only reads the files in the repository; a separate, credentialed step can deploy to a preview theme when you want one. Shopify: use the CLI in a CI/CD pipeline · Shopify: Lighthouse CI action

# .github/workflows/theme.yml
# Runs on every pull request to main. No store credentials required:
# Theme Check only reads the theme files already in the repository.
name: theme
on:
  pull_request:
    branches: [main]

jobs:
  check:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: "20"
      - run: npm install -g @shopify/cli
      # Lints Liquid and flags theme, performance and accessibility issues.
      # --fail-level error blocks the merge when a real problem is found.
      - run: shopify theme check --fail-level error

SEO and GEO ship the same reviewed way

A Shopify theme renders on the server, so the words, headings and structured data you ship in Liquid are in the HTML that both Google and AI answer engines read. That makes the theme the right place to control search and generative visibility—and the Git workflow the right way to change it without regressions.

For classic SEO the levers are familiar: accurate title and description logic, one clear H1 per template, clean internal linking, and complete structured data. Shopify’s themes emit a Product JSON-LD via the structured_data filter, but its default output is deliberately minimal—name, price, availability—so fields like brand, SKU, GTIN, images and shipping usually need adding in theme code, and Google recommends the OnlineStore subtype of Organization for a shop. Treating that JSON-LD as reviewed snippets, validated in CI, is how it stays correct as the catalogue changes. Shopify: ecommerce schema and structured data

GEO—generative engine optimization—extends the same idea to AI answer engines and shopping agents: Google’s AI Overviews and AI Mode, ChatGPT, Gemini and Copilot increasingly read storefronts and summarise or recommend products directly. Shopify has reported AI-referred traffic and AI-attributed orders rising sharply, and has been rolling out agent-facing discovery for eligible merchants. The durable levers are the ones you already control in the theme: complete, valid structured data; genuine, server-rendered product copy; correct hreflang and market handling for the UK and EU; and fast, accessible pages. Shopify: agentic commerce momentum

Recommendations for UK & EU merchants

After many UK and EU Shopify engagements, our advice is unglamorous: connect the theme to Git first, make the preview theme and the pull request non-negotiable, and only then turn up the speed with an AI agent. The leverage is real—an agent that is properly grounded ships features, fixes, SEO and GEO in hours instead of days—but it comes from the discipline around it, not from the model. That is the same standard we apply in our custom Shopify development and performance and search work.

Primary sources

• Shopify: GitHub integration for themes
• Shopify CLI: theme commands
• Shopify: CLI for themes
• Shopify: Theme Check
• Shopify: use the CLI in a CI/CD pipeline
• Shopify: ecommerce schema and structured data
• Shopify: agentic commerce momentum

Technical and operational guidance, not legal or commercial advice. Confirm current Shopify features, plan requirements and agent-program availability for UK and EU merchants before relying on them.