Menu
Git operations: branching, commit message format, pre-commit hook handling, and push policy
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Full workflow: environment setup, running experiments, reusing and implementing new components (models, datasets, plmodules, callbacks), and testing
How to load a checkpoint and run evaluation (inference only, no training)
Reference code folder conventions — storing external code and documentation for AI-assisted development context
Coding style guidelines and common pitfalls for this project
Hydra configuration file structure and conventions for models, datasets, callbacks, and training
Data format conventions for datasets and plmodules
| name | git |
| description | Git operations: branching, commit message format, pre-commit hook handling, and push policy |
Never commit or push directly to main. All changes must go through a Pull Request on a feature branch.
When creating a new branch off main, always sync local main with the remote first:
git checkout main && git pull origin main
git checkout -b your-new-branch
Only commit when explicitly requested by the user.
Pre-commit hooks run automatically on every commit. Claude should handle failures without asking the user:
git commit — hooks run automatically.git add <modified-files> then retry the same commit message.Never auto-push. Only run git push when explicitly asked by the user.