Agent skill
refactoring-12-data-versioning
Use when adding lightweight data versioning and dataset reproducibility practices.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/development/refactoring-12-data-versioning
SKILL.md
Refactoring 12: Data Versioning
Goal
Make input data changes explicit and reproducible.
Sequence
- Order: 12
- Previous: refactoring-11-ci-automation
- Next: none
Workflow
- Define dataset sources, versions, and checksums.
- Success: Each dataset has an identifiable source and version.
- Store metadata in a manifest (CSV/JSON/TOML).
- Success: Manifest captures dataset metadata and checksums.
- Separate raw data from derived artifacts.
- Success: Raw and derived data live in distinct locations.
- Record dataset version alongside experiment outputs.
- Success: Outputs reference the dataset version used.
- Prefer lightweight tracking unless DVC or similar is already in use.
- Success: Versioning stays minimal and non-disruptive.
Guardrails
- Do not commit large datasets to git.
- Avoid tooling changes that block current workflows.
- Keep versioning easy to maintain.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?