compare

Compare two Starlake project versions and output a structured diff report.

209|30|Updated Sep 18, 2021
One-click install
npx skills add https://github.com/starlake-ai/starlake --skill compare-starlake-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compare
Source: https://github.com/starlake-ai/starlake/tree/main/.agent/skills/compare
Command: npx skills add https://github.com/starlake-ai/starlake --skill compare-starlake-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly identify what changed between two Starlake project versions, enabling faster audits and rollbacks.

Core Features & Use Cases

  • Version diff: compare two project versions and surface added, removed, or modified pipelines and configurations.
  • Change visibility: highlight changes in critical components like pipelines, schemas, and transforms.
  • Use Case: when reviewing a commit or snapshot to understand the impact of changes on the data pipeline.

Quick Start

To compare two versions, run the Starlake CLI with references to the old and new project states.

Frequently Asked Questions about compare

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

FAQPage Schema
How do I compare two Starlake project versions to find pipeline and schema changes?

To compare Starlake project versions, use the CLI to reference old and new project states. It identifies differences by comparing files and configurations, outputting a structured diff report that surfaces altered pipelines, schemas, and settings.

What is the best way to review a Starlake commit for configuration changes?

Reviewing a Starlake commit requires comparing the project snapshot to a previous state. This comparison highlights changes in critical components like pipelines, schemas, and transforms, providing clear visibility into the impact on your data pipeline.

How does version diffing handle renamed or moved files in a Starlake project?

Version diffing validates common edge cases like renamed or moved files when comparing project versions. It applies structured logic to the file and configuration comparison to ensure altered pipelines and settings are accurately surfaced without false positives.

Can I use this to identify removed pipelines when auditing a Starlake project snapshot?

Yes, you can identify removed pipelines when auditing a Starlake project snapshot. The comparison process surfaces added, removed, or modified pipelines and configurations, enabling faster audits and rollbacks by showing exactly what changed between versions.