40.CI/CD drift detection

Name: Dembrandt
Author: Dembrandt

DeveloperEnterprise

Overview

Extract on every release and load into the Dembrandt App to diff against the pinned baseline. Teams that ship frequently catch visual drift before it accumulates into a rebrand.

For teams that ship frequently, manual design review cannot keep up with the pace of releases. The workflow: extract the deployed site after each release cycle, save the output, and load it into the Dembrandt App alongside the pinned baseline. The App computes a per-token diff: what changed, what drifted, what is new. CI/CD pipeline integration with automated pass/fail gating is on the Pro platform roadmap. The current workflow is: extract on release, review in App, act on the diff before the next cycle.

Extract after each release

Terminal

dembrandt app.company.com --save-output

CI step: extract and archive

# In your pipeline, after deploy:

- name: Extract design tokens

run: npx dembrandt ${{ env.SITE_URL }} --save-output --json-only

- name: Archive extraction

uses: actions/upload-artifact@v4

with:

name: tokens-${{ github.sha }}

path: output/

Agent prompt: compare two archived extractions

# Download two artifact JSONs, load both into context, then:

"Compare these two extractions from the same site.

Show the token diff as an ASCII table:

TOKEN | BEFORE | AFTER | DELTA

Flag any change above 10% with ⚠️.

Summarize what changed and whether it looks like intentional

update or unintentional drift."

Output

Token snapshots archived per release. Agent produces ASCII diff on demand, no --compare flag needed.

More in Automation

38.Docker and CI pipeline extraction 39.Track token drift 41.Design drift detection in GitHub Actions

Browse all

All recipes →

43 workflows