Carter McCann Lead forward-deployed engineer Project intake Selected briefs
Work index

Systems / Internal system / Private repository

SEO fix loop and CI gate

A board-driven agent loop that turns SEO tasks into reviewed, gated, deployed pull requests.

Year
2026
Relationship
Internal system
Role
Design and build
Diagram of the SEO fix loop: a board task goes to a maker agent, then a reviewer agent, then a shared CI gate, then deploy, with crawler findings planned to refill the queue
Fig. 01 Architecture diagram. Maker, checker, gate, deploy.
01

Overview

What it is

ComCreate maintains dozens of client sites. The loop takes a ready task from the team's board and has one agent make the smallest fix and open a draft pull request. A separate agent reviews it and merges it through a shared CI gate, which deploys from CI. It was proven end to end on a live client site.

02

Scope

What it includes

  1. 01

    A maker loop that claims one task and opens a draft pull request

  2. 02

    An independent reviewer loop with a strict merge gate

  3. 03

    A reusable CI workflow that every client repo calls

  4. 04

    A crawler that turns site issues into fixable findings

03

Role

My role

I designed and built the loop, the repo onboarding process, and the shared deploy gate, and I set up the crawler that feeds it. The work ran from June to July 2026.

04

Build

Technical notes

Maker and checker
The author and the reviewer run as separate agents on different models, so no agent approves its own change.
Deploy identity
CI deploys to Vercel with a token, so a deploy doesn't depend on who authored the commit. That lets one shared workflow cover the whole fleet.
Onboarding
Putting a repo on the gate is a minimal diff with no lockfile churn, reviewed and merged by its own loop.
Sensing
A vendored open-source Rust crawler, built with Nix, produces the findings. They map to fix types and risk tiers on a default-deny basis.
CI audit
After rollout, I audited CI across all 49 active repos in the organization and 742 runs over 30 days. The shared gate held up, and the failures were on the calling side.
  • Claude Code
  • GitHub Actions
  • Vercel
  • Rust
  • Nix
  • monday.com
05

Selected work

Development work

  1. 01 Loop Design
  2. 02 Review Gate
  3. 03 Shared CI Workflow
  4. 04 Repo Onboarding
  5. 05 Crawler Integration
  6. 06 CI Audit
06

Results

Results

  • Proven end to end on a live client site: board task, fix, pull request, merge, token-based deploy, production.