datalad-log

Trace DataLad run provenance by listing and inspecting recorded runs.

1|Updated Feb 25, 2026

Search Tags:#audit #provenance #history #traceability #dataset #datalad

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browse and audit DataLad dataset histories by listing runs, inspecting provenance, and tracing the command that produced outputs.

Core Features & Use Cases

List recorded runs with datalad log --oneline to surface the run history.
Inspect a specific run with datalad rerun --report to view the full provenance without executing the workflow.
Trace output provenance by locating commits that touched a file and retrieving the run metadata to reveal the generating command and inputs.

Quick Start

List the run history for a dataset and inspect provenance for a specific commit or file without re-running analyses.

Frequently Asked Questions about datalad-log

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

FAQPage Schema

How do I trace which command generated a file in a DataLad dataset?▼

To trace file provenance in a DataLad dataset, locate the commit that touched the file and extract run metadata using datalad rerun --report to reveal the generating command and inputs without re-executing the workflow.

What is the best way to audit DataLad run history without re-executing workflows?▼

Auditing DataLad run history without re-execution is done by listing recorded runs with datalad log --oneline and inspecting specific commits with datalad rerun --report to view full provenance details.

How do I list all recorded runs in a DataLad dataset?▼

You list recorded DataLad runs by applying datalad log --oneline to the dataset, which surfaces the run history and allows you to identify commits for subsequent provenance inspection.

Can I inspect DataLad provenance details for a specific commit without running the analysis again?▼

Yes, you can inspect DataLad provenance for a specific commit without re-running by applying datalad rerun --report, which extracts and presents the run metadata directly from the recorded history.

Why do I need provenance traceability for dataset debugging workflows?▼

Dataset provenance traceability is needed for debugging workflows because it identifies the exact command and inputs that generated an output across commits, allowing you to isolate data lineage issues without re-execution.