Menu
Use when pushing changes in a repository that contains git submodules, especially when the submodule has its own commits that must not be left stranded. Triggers include "push", "git push", "submodule", "commit submodule", "workspace push"
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when turning recent agent-session evidence into durable skill updates. Triggers: "consolidate lessons", "update skills from sessions", "prevent repeated fixes", "recurring mistakes", "capture workflow learnings"
Use when running workloads on LUMI supercomputer, including GPU job submission, PyTorch with ROCm/AMD MI250X, container workflows, and LUMI-specific Slurm configuration. Triggers: "LUMI", "MI250X", "ROCm", "AMD GPU", "CSC", "LUMI-G"
Use when integrating W&B experiment tracking into ML training pipelines, including logging strategy, run configuration, and online/offline mode management. Triggers: "W&B", "wandb", "weights and biases", "experiment logging", "wandb.log", "wandb.init", "training dashboard"
"Use when extracting Overleaf login cookies from Chrome on macOS for the VSCode Overleaf Workshop extension. Decrypts Chrome's cookie store and outputs the session cookie in the exact format the extension expects. Triggers: "overleaf cookie", "overleaf login", "overleaf workshop cookie", "get overleaf cookie", "vscode overleaf login"
Use when preparing to launch any remote or multi-GPU ML experiment. Triggers include "preflight", "sanity check", "launch validation", "before training", "GPU check", "dataset check", "environment check"
Use when evaluating academic papers or surveying a research topic. Gathers venue, citations, GitHub stats, social buzz, reproducibility, and author signals to produce a scored markdown report. Triggers: "evaluate paper", "paper review", "research survey", "literature review", "is this paper good", "find papers on", "compare papers", "paper impact"
| name | git-submodule-push |
| description | Use when pushing changes in a repository that contains git submodules, especially when the submodule has its own commits that must not be left stranded. Triggers include "push", "git push", "submodule", "commit submodule", "workspace push" |
git push)Always push submodule first, then outer repo, then mirror.
Submodule first
git -C <submodule-path> add -A
git -C <submodule-path> commit -m "<message>"
git -C <submodule-path> push
Outer repo (bumps the submodule pin)
git add <submodule-path>
git commit -m "<message>"
git push
Mirror clone (if configured)
git -C <mirror-path> pull --ff-only
| Mistake | Fix |
|---|---|
| Pushing outer repo before submodule | Submodule commits are stranded; reverse the order |
Forgetting git add <submodule-path> | Pin doesn't update; outer repo still points to old commit |
Using git push --recurse-submodules=on-demand without checking | Fails silently if submodule remote rejects; explicit push is safer |
| Skipping the mirror sync | Standalone clone drifts out of date |
.gitmodules or the gitlink directly instead of git add <submodule-path>