What problem does it solve? Editing dotfiles in a Guix Home repository does not take effect immediately because deployed files are read-only store symlinks, and naive edits, deletions, or service restarts silently fail or cause irreversible damage. This Skill encodes the verified workflows, invariants, and debugging protocols for working safely inside the Guix-configs repository. ## Core Features & Use Cases - Dotfiles deployment verification: Enforces the three-step change-source, run blue home, verify store hash workflow, including the rule that blue home must run from the repository root and that running shepherd daemons need manual herd restart. - Service and desktop debugging: Covers shepherd service diagnosis (cached PID traps, --replace self-kick loops, multiple home-shepherd instances), gpg-agent/pinentry absolute store path fixes, niri environment variable injection for IME, and Electron Wayland IME version-specific flags. - Safe editing and recovery protocols: Multi-line edit safety via python str.replace, worker delegation with baseline diffs, AGENTS.md regeneration via blue structor, GNU Stow two-tier deployment, and git history restoration of deleted dotfiles. - Use Case: When a user reports that fcitx input stopped working in an Electron app or that gpg asks for passwords in the TTY instead of pinentry-qt, this Skill provides the exact diagnostic commands and the verified fix path. ## Quick Start Diagnose why my gpg passphrase prompt falls back to TTY instead of pinentry-qt and fix the gpg-agent configuration using absolute store paths.