EmanuProds/dotfiles / skills/managed-config-drift
managed-config-drift"
UnverifiedAudit drift between live Linux configuration, version-controlled configuration repositories, symlink farms, and packaged defaults. Use when configuration ownership is unclear, a desktop behaves differently from its repo, symlinks may be broken, generated files may be stale, or an update may have overwritten local state. Default to reporting and do not synchronize or replace files automatically.
Managed configuration drift
Build an ownership map before comparing content. Identify the live path, intended source repository, generated-file contract, packaged default, and deployment mechanism such as symlinks, copy scripts, GNU Stow, or hooks.
Use scripts/compare-trees.py LIVE=MANAGED [...] for bounded tree comparisons. It reports missing paths, type changes, symlink-target changes, and content differences without modifying either tree. Use --exclude NAME for caches, secrets, runtime state, or generated artifacts that the repository explicitly excludes.
Classification
- Broken ownership: dangling link, missing source, wrong owner, or unexpected writable target.
- Uncommitted live drift: live content differs from its declared managed source.
- Expected local state: secrets, caches, device state, or host-specific overrides documented as untracked.
- Generated drift: output differs because its declared generator has not run.
- Packaged-default drift: an upstream update changed a default that the local overlay depends on.
Read repository guidance and generator commands before judging a difference. Never copy, replace, delete, relink, refresh Omarchy configuration, or run a generator merely to make the audit clean. Establish an owner and direction for each reconciliation. Keep audit-only requests read-only. When the user already authorized reconciliation of the named paths, continue the scoped repair, preserve recoverable prior state, and verify the resulting ownership and behavior. Ask only for missing authority or an unresolved consequential direction; do not request the same authorization again.
Use omarchy for configuration owned by an identified Omarchy installation, not arbitrary Hyprland files. Use nixos when modules generate the live paths; reconcile the declarative source instead of replacing store symlinks. Use sensitive-info-audit before adding previously untracked live configuration to Git.
Use arch-update-recovery when drift was introduced by an Arch-family package transaction, .pacnew/.pacsave files, a snapshot rollback, or boot-chain regeneration. Use backup-restore-verification to prove a managed source can actually be recovered; a clean comparison alone does not prove that.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 464k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |