菜单
Reference code folder conventions — storing external code and documentation for AI-assisted development context
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Git operations: branching, commit message format, pre-commit hook handling, and push policy
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)
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 | reference |
| description | Reference code folder conventions — storing external code and documentation for AI-assisted development context |
docs/reference/ stores reference external code and documentation. These files serve as helpful context for AI-assisted code generation and development — you can attach them to your conversation so the AI can draw on external codebases.
check-added-large-files pre-commit hook is disabled in this folder, so large files can be committed freely.README.md entry in docs/reference/ to document each file:- file-name.txt
- Source: name of external source
- Content: brief description of what this contains