菜单
Guidelines when managing Nix configuration
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | nix |
| description | Guidelines when managing Nix configuration |
# Standard module structure used in this repo
{ config, pkgs, ... }: {
programs.<name> = {
enable = true;
# options...
};
}
Always verify with home-manager switch --flake .#<host> after changes.
# 1. Add to home.packages or the appropriate programs.<name> block
# 2. Run:
home-manager switch --flake .#<host>
# 3. Verify the binary is available:
which <package>
with pkgs; at the top level — it pollutes scope and makes deps unclearpkgs.writeShellScriptBin for complex scripts — use a dedicated derivation insteadnix.conf or pass --accept-flake-config# 1. Run update (only if this command is defined in the flake)
nix run .#update
# 2. Stage changes
git add .
# 3. Commit (English only)
<type>: <summary>
# 4. Push to remote
git push
nix flake update
# nixpkgs overlay etc.
nix build .#<target>
# For home-manager (replace host with config name)
home-manager switch --flake .#<host>
Use this skill whenever the user wants to merge the main branch into their current branch. Triggers include phrases like "merge main", "mainをマージ", "mainを取り込む", "mainに追従", "sync with main", "mainの変更を取り込みたい", or any request to bring changes from main into a feature/working branch. Always use this skill — do not improvise git commands without it.
Template and notes when creating or updating SKILL.md files under skills/
Perspectives and rules when conducting a code review
Template, notes, and procedure when creating a Pull Request
Rules for Git commits, pushes, and PR creation
When creating, editing, or debugging GitHub Actions workflow YAML files