dots-remove

Remove tracked configs from the dots symlink management system.

Updated Jun 17, 2025
One-click install
npx skills add https://github.com/nikbrunner/dots --skill dots-remove
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dots-remove
Source: https://github.com/nikbrunner/dots/tree/main/common/.agents/skills/dots-remove
Command: npx skills add https://github.com/nikbrunner/dots --skill dots-remove

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remove a config from the dots symlink management system, ensuring it is no longer tracked or deployed.

Core Features & Use Cases

  • Identify a config in the dots repository or in symlinks.yml and remove it from tracking.
  • Clean up the associated symlink and config file references so deployments no longer include the removed item.
  • Use case: when a configuration becomes obsolete or should be deprecated from dots management.

Quick Start

Provide the path to the config (symlink path or dots repo path) and follow the prompts to complete the removal.

Frequently Asked Questions about dots-remove

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

FAQPage Schema
How do I remove a config from dotfiles symlink tracking?

Removing a config from dotfiles tracking requires providing the symlink path or dots repository path. The system validates the target in symlinks.yml, updates tracking, deletes the symlink, and removes the repository entry when confirmed.

How do I clean up obsolete configuration symlinks from my home directory?

Cleaning up obsolete configuration symlinks involves validating the target path in symlinks.yml and deleting the corresponding symlink from your home directory. This ensures deployments no longer include the removed configuration item.

Can I delete a config file from the dots repository without removing the symlink?

Deleting a config file from the dots repository independently of the symlink is supported. The system updates the tracking in symlinks.yml and deletes the repository-backed entry in common/ only when explicitly confirmed during the removal process.

What is the best way to stop tracking a dotfile in configuration management?

The best way to stop tracking a dotfile in configuration management is to use a removal process that validates the symlinks.yml entry, deletes the associated symlink, and optionally removes the config from the repository to prevent future deployments.

Does dots-remove work with both symlink paths and repository paths?

Dots-remove works with both symlink paths in the home directory and repository-backed entries in common/. It validates the provided path against symlinks.yml to accurately locate and remove the targeted configuration from tracking.