Skip to content

LeandroBenjaminL/lend-ai / skills/shared-git-data

shared-git-data

Unverified

Git for data science — versioning notebooks, datasets, and pipelines. DVC, nbstripout, .gitignore, and reproducible data workflows. Trigger: When working with git in data science projects, committing notebooks, managing datasets, or setting up a data repo.

Skill: shared-git-data

Git for data science. Different from code — data needs its own rules.

Trigger

  • Starting a data project and creating the repo
  • Committing a notebook and you don't want to push megabytes of outputs
  • Should the dataset be in the repo or not?
  • You need to version pipelines without versioning heavy data

Workflow LEND

  1. ANALYZE ├── Project: analysis, pipeline, dashboard? ├── Data: how big? can it go in the repo? (< 100 MB) ├── Notebooks: outputs included or stripped? └── Collaboration: solo or team?

  2. OFFER (Senior Menu) ├── A) Standard git — code + clean notebooks + small data (< 100 MB) ├── B) Git + DVC — large data versioned outside the repo └── C) Git + nbstripout — notebooks without outputs, clean diffs

  3. CHOOSE → user confirms

  4. EXECUTE ├── .gitignore: .venv/, pycache/, *.pyc, .env, data/raw/ ├── nbstripout: git config filter.nbstripout.extrakeys 'metadata.kernel' ├── DVC: dvc init && dvc add data/raw/dataset.csv && git add data/raw/dataset.csv.dvc ├── README.md with reproduction instructions ├── requirements.txt frozen ├── Commits in English US, semantic (feat, fix, chore) └── Branch + PR workflow for data pipelines

  5. VERIFY ├── .gitignore covers what shouldn't be in the repo ├── Notebooks can be diffed (no outputs) └── A fresh git clone && pip install is enough to start

  • Save decisions and changes to Engram (mem_save)
  • Check if README, AGENTS.md, or ARCHITECTURE.md need updating
  • If docs changed → update them in the same PR/commit
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexUnverifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 117kUpdated Claude CodeCodexUnverifiedInstall