Skip to content

gpsaggese/helpers / .claude/skills/tutorial_in_60_mins.propagate_docker_changes

tutorial_in_60_mins.propagate_docker_changes

Verified

Sync tutorial and class-project Docker files to match project_template

Overview

  • <SRC_DIR> = class_project/project_template

This skill supports two modes:

  • Full sync: Make all Docker files across projects match project_template
  • Last-commit sync: Propagate only the changes from the most recent commit in project_template

Mode A: Full sync

  • Find each target directory <DST_DIR>: every directory under class_project/ (other than <SRC_DIR> itself) that already has a Dockerfile
    > find class_project -mindepth 2 -maxdepth 2 -name Dockerfile \
        -not -path "class_project/project_template/*"
    
  • For each <DST_DIR> found this way, make the Docker files <DST_DIR>/docker_*.sh, <DST_DIR>/Dockerfile, <DST_DIR>/run_jupyter.sh as similar as possible to the corresponding ones in <SRC_DIR>
    • The goal is to reuse functions and factored out code (e.g., from class_project/project_template/utils.sh)
  • If you are not sure about what the changes are
    • Summarize the changes for the user in bullet points
    • Ask the user to confirm

Mode B: Last-commit sync

  • Use this mode when you only need to propagate the most recent changes

Check the Last Commit

  • Look at the changes from the last git commit in <SRC_DIR>
  • Summarize the changes for the user in bullet points
  • If you are not sure about what the changes are, stop and ask the user to confirm

Propagate the Changes

  • Propagate the changes in the Docker system from <SRC_DIR> to every <DST_DIR> found via the find command in Mode A

Preserve Behavior

  • Make sure not to change the behavior unless needed

Update the Docker Docs

  • Update class_project/project_template/docker_scripts.README.md explaining how this project uses Docker to build and execute containers given the new changes

Verification (both modes)

  • All the docker_*.sh scripts work, run either directly or through the relevant pytest unit tests
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 318kUpdated Claude CodeCodexVerifiedInstall
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 CodeCodexVerifiedInstall