apply-dconf

Synchronize GNOME dconf settings into a declarative Nix Home Manager configuration.

4|Updated Feb 20, 2023
One-click install
npx skills add https://github.com/Hayao0819/dotfiles --skill apply-dconf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apply-dconf
Source: https://github.com/Hayao0819/dotfiles/tree/main/.claude/skills/apply-dconf
Command: npx skills add https://github.com/Hayao0819/dotfiles --skill apply-dconf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps synchronize GNOME dconf settings with a declarative Nix Home Manager configuration, enabling reproducible GNOME environments by capturing the current dconf state and persisting it into the nix configuration.

Core Features & Use Cases

  • Dump current dconf settings: collect the current dconf state (e.g., dconf dump /) for versioned configuration.
  • Compare with existing config: identify differences between the live state and dconf-generated.nix.
  • Update dconf-generated.nix: propagate the current settings into the declarative config.
  • Apply across machines: ensure consistent GNOME extensions, keybindings, and UI preferences via Home Manager.

Quick Start

Run the apply-dconf workflow to generate and update dconf-generated.nix from the current dconf state.

Frequently Asked Questions about apply-dconf

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync GNOME dconf settings to a declarative Nix Home Manager configuration?

To sync GNOME dconf settings to a declarative Nix Home Manager configuration, the workflow dumps the current dconf state, compares it with the existing dconf-generated.nix file, and updates the Nix configuration to capture your current desktop environment preferences.

Can I synchronize GNOME extensions and keybindings across multiple machines using Nix?

Yes, you can synchronize GNOME extensions and keybindings across multiple machines by dumping current dconf settings into a declarative Nix Home Manager configuration, ensuring your interface settings and preferences remain reproducible across different systems.

What is the best way to capture live GNOME preferences into a Nix configuration file?

The best way to capture live GNOME preferences into a Nix configuration file is running a dconf dump command to extract the current state and propagating those settings directly into your dconf-generated.nix file for version control.

Does Home Manager validate dconf changes before committing them to the Nix config?

Yes, the workflow validates changes before committing them to the Nix config. It reads the dconf-generated.nix file and checks the differences between the live dconf state and the existing declarative configuration to ensure accuracy.

Why should I use declarative Nix configuration for GNOME dconf instead of manual tweaks?

Using declarative Nix configuration for GNOME dconf ensures your desktop preferences are reproducible and version-controlled. It prevents configuration drift by capturing live dconf state and persisting it into a maintainable Nix Home Manager file.

What do I need to dump dconf settings for a Nix Home Manager workflow?

You need the dconf dump command available on your system to extract the current GNOME state. The workflow reads this dumped data and updates the dconf-generated.nix file to integrate your live settings into the declarative Nix configuration.