What problem does it solve? Deciding where a new config file belongs in a dotfiles repository and wiring up symlinks by hand is error-prone: secrets can leak into the public side, mixed directories get over-linked, and name collisions silently overwrite files. This Skill guides the full adoption (or removal) workflow with explicit judgment criteria. ## Core Features & Use Cases - Managed adoption: Brings a config file under dotfiles management via scripts/adopt_dotfile.sh, choosing between the public home/ (git) and private private/ (encrypted archive) placements. - Secret extraction: Scans file contents before adoption and moves real credential values into ~/.secrets/env, replacing them with references. - Safety checks: Handles mixed-content parent directories via PARTIAL_DIRS, detects name collisions between home/ and private/, and triggers verification skills afterward. - Use Case: You want your .codex/config.toml backed up with your dotfiles. The Skill inspects it, decides it belongs in private/, strips any API keys, runs the adoption script, and reports the resulting symlink. ## Quick Start Ask the assistant to adopt ~/.codex/config.toml into dotfiles management and let it decide the placement.
