Data Data Versioning
Use when the user asks about data versioning with DVC or lakeFS, Git-like branches for data, data snapshots, rollback of a bad load or reproducible training data. Produces versioning workflow, branching model and reproducibility checks. Not for Iceberg/Delta time travel (use data-data-lake) or experiment logging (use ml-experiment-tracking).
Install
npx skills add j4flmao/agent-skills --skill data-data-versioninggit clone --depth 1 https://github.com/j4flmao/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/data/data-versioning ~/.claude/skills/data-data-versioningPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Data Data Versioning ## Purpose Implement data versioning with DVC or LakeFS for reproducibility, branching, diff, rollback, and experiment tracking across data pipelines and ML workflows. ## Agent Protocol ### Trigger Exact user phrases: "data versioning", "DVC", "LakeFS", "data lineage", "Git-like for data", "data reproducibility", "data branching", "data diff", "data snapshot", "experiment reproducibility", "data rollback", "data version control". ### Input Context - Data storage platform (S3, GCS, ADLS, MinIO) - ML/analytics pipeline framework - Existing Git workflow for code - Team size and collaboration patterns - Experiment tracking needs - Compliance requirements for data lineage ### Output Artifact Data versioning strategy with DVC or LakeFS, branching model, experiment reproducibility workflow, data diff and rollback procedures. ### Response Format ```yaml # Versioning tool selection # Branching model # DVC/LakeFS configuration # Experiment tracking setup # Data diff + rollback workflow ``` No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick. ### Completion Criteria - [ ] Versioning tool selected (DVC vs LakeFS) with rationale - [ ] Branching model defined for data development - [ ] DVC or LakeFS configured with remote storage - [ ] Data diff and rollback procedures documented - [ ] Experiment reproducibility workflow established - [ ] Data lineage tracked from source to output
Details
- Skill name
data-data-versioning- Repository
- j4flmao/agent-skills
- Path
skills/data/data-versioning/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Data Data Versioning skill do?
Use when the user asks about data versioning with DVC or lakeFS, Git-like branches for data, data snapshots, rollback of a bad load or reproducible training data. Produces versioning workflow, branching model and reproducibility checks. Not for Iceberg/Delta time travel (use data-data-lake) or experiment logging (use ml-experiment-tracking).
How do I install the Data Data Versioning skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add j4flmao/agent-skills --skill data-data-versioning. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Data Data Versioning popular?
It lives in j4flmao/agent-skills, which has 45 GitHub stars and 6 forks.
Related skills
Agent Observability
45j4flmao/agent-skills
Use when the user asks about agent observability, tracing agent reasoning, debugging an agent loop, OpenTelemetry GenAI spans for LLM calls, LLM cost tracking per agent, agent audit logs or hallucination/eval monitoring in production. Produces instrumentation config, trace schema, dashboards, alerts and cost attribution. Not for generic service tracing without LLMs (use devops-opentelemetry).
AI Agent Architectures
45j4flmao/agent-skills
Use when the user asks to build an AI agent, design an agent that calls tools and keeps memory, write an agent system prompt or pick an agent framework (Claude Agent SDK, OpenAI Agents SDK, LangGraph). Produces an architecture brief covering loop, tools, memory, guardrails and evals, routing depth to child skills. Not for workflow patterns (use ai-agentic-workflows).
AI Agent Core Loop
45j4flmao/agent-skills
Use when the user asks about the agent loop, ReAct vs plan-and-solve, re-planning, Reflexion, an agent stuck in a loop, max iterations or termination conditions. Produces a loop spec or patch with state, success predicate, caps and no-progress detection. Not for overall agent design (use ai-agent-architectures) or tool schemas (use tool-calling-principles).
Dev Loop Changelog Generator
45j4flmao/agent-skills
Use when the user asks to generate a CHANGELOG.md, release notes, semantic versioning bumps, or automate changelogs from conventional commits with release-please, changesets or semantic-release. Produces changelog entries and release automation config. Not for PR descriptions (use dev-loop-pr-writer) or branching strategy (use dev-loop-git-workflow).
Code Review
45j4flmao/agent-skills
Use when the user asks to review this code, review a pull request for bugs, give feedback on an implementation, check a diff, or asks LGTM?. Produces a structured review with MUST/SHOULD/CONSIDER findings on correctness, security, performance and tests. Not for finding a bug's root cause (use dev-loop-debugging-strategy) or writing the PR text (use dev-loop-pr-writer).
Dev Loop Git Workflow
45j4flmao/agent-skills
Use when the user asks about git branching strategy, trunk-based development vs git flow, rebase vs merge, a messy rebase or merge conflict, commit conventions, squash or history cleanup. Produces team git conventions and commands. Not for multi-team release trains (use enterprise-release-engineering) or changelogs (use dev-loop-changelog-generator).
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.