datalad-diff

Compare file-level state differences in DataLad datasets across revisions.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/bcmcpher/my-skills --skill datalad-diff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: datalad-diff
Source: https://github.com/bcmcpher/my-skills/tree/main/plugins/datalad-cli/skills/datalad-diff
Command: npx skills add https://github.com/bcmcpher/my-skills --skill datalad-diff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables you to quickly identify which files have changed between two points in a DataLad dataset's history, surfacing file-level state changes without inspecting content.

Core Features & Use Cases

  • File-level diffs: See added, modified, or deleted files between revisions, commits, or branches.
  • Context-aware guidance: Works when a .datalad/ dataset is present and can indicate when the dataset isn't found.
  • Use Case: When auditing a project with DataLad, compare the working tree against a known good revision to track changes.

Quick Start

Provide two revisions or a range to compare, then ask the tool to run datalad diff to display the results.

Frequently Asked Questions about datalad-diff

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

FAQPage Schema
How do I compare file changes between two commits in a DataLad dataset?

To compare file changes in a DataLad dataset, provide two revisions, commits, or branches to run datalad diff, which reports added, modified, or deleted files without displaying content diffs.

Can I compare the working tree against a specific revision using datalad diff?

Yes, datalad diff supports working-tree versus specific-commit comparisons, allowing you to track uncommitted file-level state changes against a known good revision in your DataLad dataset.

What does a DataLad diff show when auditing dataset history?

A DataLad diff shows file-level state differences, surfacing which files were added, modified, or deleted across revisions or branches while omitting the actual content diffs for quick auditing.

Do I need a .datalad directory present to compare dataset histories?

Yes, a .datalad directory must be present for context-aware guidance, as the tool relies on it to locate the dataset and can indicate when the dataset is not found.

Does datalad diff modify my dataset when comparing file states?

No, datalad diff operates strictly in read-only mode to compute and report file-level changes across revisions, commits, or branches without modifying your DataLad dataset.

What is the best way to track deleted or added files across DataLad branches?

The best way to track added or deleted files across DataLad branches is to provide a revision range to datalad diff, which computes file-level state differences without inspecting content.