content-diff

Compare two EDS page versions and generate author-friendly change reports.

Updated May 14, 2026
One-click install
npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill content-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-diff
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/content-diff
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill content-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes guesswork by producing a clear, author-friendly diff between two versions of an Adobe Edge Delivery Services (EDS) page, including content, blocks, media, and meaningful metadata changes.

Core Features & Use Cases

  • Preview vs Live comparison: Shows what will change on the next publish by diffing the .aem.page (preview) against the .aem.live (live) version.
  • Two-URL and branch comparisons: Compares any two explicit EDS URLs or the same page across two branches to validate edits and consistency.
  • Risk-aware change reporting: Classifies change scope and highlights potential SEO, performance, and accessibility impacts while filtering environment-driven metadata noise (e.g., canonical domain differences).

Quick Start

Use the content-diff skill to compare a page’s preview and live versions and generate a detailed change report for review before publishing.

Frequently Asked Questions about content-diff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I compare preview versus live versions of an Adobe EDS page?

Comparing two Adobe EDS page versions requires fetching full and plain HTML representations to identify meaningful changes in authored content, blocks, media, and metadata. This generates an author-friendly report showing exactly what will change before publish.

What is the best way to audit block changes before publishing in Edge Delivery Services?

Auditing block changes in Edge Delivery Services involves diffing section content and block structures between two page versions. This process classifies change scope and highlights potential SEO, performance, and accessibility impacts while filtering environment-specific metadata noise.

Can I compare the same EDS page across two different branches?

Yes, you can compare the same EDS page across two different branches. The content diff process supports same-page branch comparisons, two explicit URL comparisons, and preview-versus-live diffs to validate edits and ensure publishing consistency.

Does an EDS content diff filter out environment-specific metadata differences?

Yes, an EDS content diff filters out environment-specific metadata differences such as canonical domain variations. This ensures the author-friendly report focuses only on meaningful changes in authored content, blocks, and media rather than environment-driven noise.

How does a content diff assess SEO risk assessment for EDS page updates?

A content diff assesses SEO risk by classifying the scope of changes between EDS page versions and highlighting potential SEO, performance, and accessibility impacts. This risk-aware reporting removes guesswork by showing exactly what will change before publish.