datalad-save

Automate saving changes in DataLad datasets with datalad save.

1|Updated Feb 25, 2026

Search Tags:#automation #git #dataset #version-control #data-management #datalad

Ready to run

npx skills add https://github.com/bcmcpher/my-skills --skill datalad-save

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: datalad-save
Source: https://github.com/bcmcpher/my-skills/tree/main/plugins/datalad-cli/skills/datalad-save
Command: npx skills add https://github.com/bcmcpher/my-skills --skill datalad-save

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates saving changes inside a DataLad dataset by replacing git add and git commit. DataLad datasets require a specialized save command to handle both git-tracked and annexed files, and this skill ensures proper recording of changes within that context.

Core Features & Use Cases

Replaces git add + git commit inside DataLad datasets to correctly handle annexed and git-tracked files.
Shows a live preview of changes with datalad status and enforces a meaningful commit message.
Supports path-scoped saves and returns the resulting commit hash for traceability.

Quick Start

Provide a meaningful commit message and run this skill to save all changes in the current DataLad dataset.

Frequently Asked Questions about datalad-save

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

FAQPage Schema

How do I save changes in a DataLad dataset instead of using git add and git commit?▼

To save changes in a DataLad dataset, you must use a specialized command to correctly record both git-tracked and annexed files, replacing the standard git add and git commit workflow. This skill automates that process and returns the commit hash.

Why does git commit not work properly for annexed files in a DataLad dataset?▼

Git commit does not work for annexed files in a DataLad dataset because DataLad requires a specialized save command to handle both git-tracked and annexed files correctly. This ensures all modifications are properly recorded within the dataset context.

Do I need to provide a commit message when saving changes to a DataLad dataset?▼

Yes, you need to provide a meaningful commit message to save changes to a DataLad dataset. The process enforces this requirement to ensure traceability before executing the save command with an optional path scope.

Can I preview changes before saving a DataLad dataset?▼

Yes, you can preview changes before saving a DataLad dataset. The process uses datalad status to show a live preview of modifications, ensuring you know exactly what git-tracked and annexed files will be recorded.

Does this DataLad save workflow work in a plain git repository?▼

Yes, this DataLad save workflow works in a plain git repository by falling back to a standard git workflow. If the target directory is not a DataLad dataset, it automatically adapts to handle standard git-tracked files.

Can I save only a specific path within my DataLad dataset?▼

Yes, you can save only a specific path within your DataLad dataset. The save command supports an optional path scope, allowing you to target specific directories or files while still handling both git-tracked and annexed data.