메뉴
Audit NixOS impermanence state — find files still on the current filesystem device. Use when the user wants to check for untracked files, audit impermanence, or runs /impermanence-audit.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when producing, editing, or reviewing Traditional Chinese technical writing, including comments, documentation, explanations, and Chinese answers that must avoid translationese, casual phrasing, template language, and weak logic.
去除文字中的 AI 生成痕跡。適用於編輯或審閱文字，使其聽起來更自然、更像人類書寫。 基於維基百科的「AI 寫作特徵」綜合指南。偵測並修復以下模式：誇大的象徵意義、 宣傳性語言、以 -ing 結尾的膚淺分析、模糊的歸因、破折號過度使用、三段式法則、 AI 詞彙、否定式排比、過多的連接性短語。
Universal coding standards, best practices, and patterns. Use when developing in any language — triggers on TypeScript, JavaScript, React, Node.js, Python, Nix, ruff, pyright, pytest, uv, flake.nix, justfile, just, recipes, and general code quality topics.
Use when writing git commit messages, reviewing commits, or setting up commit conventions. Triggers on commit, git commit, commit message, changelog, semantic versioning.
A formal evaluation framework for Claude Code sessions, implementing eval-driven development (EDD) principles.
Docker-in-Docker with network_mode host for multi-node simulation
| name | impermanence-audit |
| description | Audit NixOS impermanence state — find files still on the current filesystem device. Use when the user wants to check for untracked files, audit impermanence, or runs /impermanence-audit. |
| allowed-tools | Bash(sudo:*), Bash(bash:*), Bash(nix:*), Read, Edit, Glob, Grep |
Scan the root filesystem with find -xdev and identify files still on the same device as /. These files would be lost on reboot when impermanence resets the root filesystem.
sudo impermanence-audit efficacy38
Interface:
sudo impermanence-audit efficacy38 gaming.find -xdev plus device-number filtering.Review the untracked files and categorize them:
| Category | Action |
|---|---|
| Application state/config | Add to the appropriate feature module's environment.persistence |
| Transient/cache files | Safe to ignore — add to ~/.config/impermanence-audit/ignore if noisy |
| System service data | Add to the system module (usually features/system/boot.nix) |
| Unknown | Investigate what created the file before deciding |
Persistence paths are declared across feature modules. Match the file to its feature:
| Path pattern | Module file |
|---|---|
Desktop app configs (~/.config/app, ~/.local/share/app) | flake-modules/modules/features/desktop/common.nix |
Dev tools (~/.kube, .local/share/direnv, etc.) | flake-modules/modules/features/devpack/tools.nix |
Editor data (~/.local/share/nvim) | flake-modules/modules/features/devpack/editor.nix |
System services (/var/lib/*, /etc/*) | flake-modules/modules/features/system/boot.nix |
| KDE state | flake-modules/modules/features/desktop/kde.nix |
| Steam/gaming | flake-modules/modules/features/desktop/steam.nix |
| Browser profiles | flake-modules/modules/features/desktop/zen.nix |
The pattern for adding a user directory to a feature module:
# Inside the module's config block, guarded by impermanence check:
config = lib.mkIf (cfg.enable && config.my.system.impermanence.enable) {
environment.persistence."/persistent/system".users."efficacy38" = {
directories = [
".config/new-app"
".local/share/new-app"
];
};
};
For system-level paths:
environment.persistence."/persistent/system" = {
directories = [
"/var/lib/new-service"
];
};
After adding persistence declarations:
nh os switch --hostname=stella
Then re-run the audit to confirm the paths are now covered.