dotfiles-stow

Guide safe editing of GNU Stow-managed dotfiles in version-controlled source paths.

5|Updated Jan 14, 2025
One-click install
npx skills add https://github.com/timmo001/dotfiles --skill dotfiles-stow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dotfiles-stow
Source: https://github.com/timmo001/dotfiles/tree/main/agents/.config/opencode/skills/dotfiles-stow
Command: npx skills add https://github.com/timmo001/dotfiles --skill dotfiles-stow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures proper handling and editing of user configuration files managed by GNU Stow, preventing manual errors and ensuring consistency.

Core Features & Use Cases

  • Configuration Management: Guides users to modify only source paths within version-controlled dotfiles repositories.
  • Workflow Enforcement: Promotes using the dot command for stow, update, and validation tasks instead of ad-hoc manual changes.
  • Use Case: When a user needs to update their .zshrc or neovim config, they are instructed to edit the source files in the repo and run dot stow to apply changes safely.

Quick Start

Follow the instructions to modify configuration files inside the source repositories and run dot stow to apply updates.

Frequently Asked Questions about dotfiles-stow

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

FAQPage Schema
How do I safely manage dotfiles with GNU Stow under version control?▼

You can safely manage dotfiles by modifying only the source files inside your version-controlled repository and running a dedicated command like `dot stow` to apply changes, ensuring you never edit live configuration files directly.

What is the correct workflow for updating zshrc or neovim config managed by Stow?▼

The correct workflow for updating configuration files like .zshrc or neovim config is to edit the source files in your dotfiles repository and then run `dot stow` to safely apply the updates to your system.

Why should I use a stow command instead of editing live config files directly?▼

You should use a stow command instead of editing live config files to enforce consistent workflows and prevent manual errors. Modifying source paths under version control ensures your configuration changes are tracked and safely applied.

Can I use ad-hoc manual changes for configuration files tracked in a dotfiles repository?▼

Ad-hoc manual changes to configuration files are not recommended for dotfiles repositories. You should use the `dot` command for stow, update, and validation tasks to ensure safe handling and consistent application of your version-controlled configurations.

When do I need to run dot stow after modifying my configuration files?▼

You need to run `dot stow` immediately after modifying any source configuration files in your repository. This command applies your tracked changes to the live system safely, completing the workflow enforcement cycle.