菜单
Build the NixOS system derivation, analyze build errors, and automatically apply fixes in a loop until the build succeeds. USE WHEN the user wants to build and fix errors automatically, or mentions deploying, building, or fixing build errors.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | NixOSBuild |
| description | Build the NixOS system derivation, analyze build errors, and automatically apply fixes in a loop until the build succeeds. USE WHEN the user wants to build and fix errors automatically, or mentions deploying, building, or fixing build errors. |
| argument-hint | <hostname> <worktree> |
You automatically build the NixOS system and fix build errors in an iterative loop until the build succeeds.
Parse Arguments: Extract hostname and worktree from ARGUMENTS. Ask for any missing arguments.
<hostname> — NixOS configuration to build. Valid: fullykubed-tower, fullykubed-mini-pc<worktree> — Worktree directory name to build from (e.g., main, my-feature-branch)Gather Context: Verify the worktree directory exists at @home@/repos/nixos-config/<worktree>/. If not, list available worktrees and ask the user:
git -C @home@/repos/nixos-config/main worktree list
Select Workflow: Route to the appropriate workflow based on the user's intent (see Workflow Routing table below).
Execute Workflow: Report to the user which workflow is running and for which hostname/worktree. You MUST read the selected workflow document completely before proceeding. Since this is a system-level skill, read it relative to this SKILL.md file: ./workflows/<WorkflowName>.md
Report Results: The workflow handles its own reporting.
| Workflow | Trigger Words | When to Use |
|---|---|---|
| Build | "build", "deploy", "fix build", "auto fix", "build errors", "nix build", "rebuild", "fix errors" | User wants to build the NixOS system and automatically fix any build errors that occur |
| ReviewAutofixes | "review", "approve", "review fixes", "approve fixes", "review autofixes", "check fixes" | User wants to review accumulated autofixes — does not block the Build workflow; this is an on-demand review of previously applied fixes |
Test NixOS configuration changes using the feedback ladder — from instant syntax checks to full system builds. USE WHEN the user wants to verify, test, or check NixOS changes before deploying.
Review and fix documentation surprises discovered by the surprise hook. USE WHEN the user wants to fix documentation issues, review surprises, or address items in .claude/surprises/.
Query systemd journal logs, check service status, diagnose failed units, and analyze boot performance. USE WHEN investigating system issues, service failures, checking logs, or when the user asks about systemd services or journal entries.
Browser automation for development testing, web scraping, and UI verification. USE WHEN you need to interact with web pages, verify UI changes, take screenshots, or extract data from websites.
Systematically explore and test a web application to find bugs, UX issues, and other problems. USE WHEN the user wants to quality-test a web app, find issues, dogfood a product, or produce a structured bug report with reproduction evidence.
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) via Chrome DevTools Protocol. USE WHEN the user needs to interact with an Electron desktop app, automate a native app, connect to a running Electron app, or test an Electron application.