using-dodot

Manage dodot dotfiles deployments, inspections, and pack maintenance.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/arthur-debert/dodot --skill using-dodot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-dodot
Source: https://github.com/arthur-debert/dodot/tree/main/skills/using-dodot
Command: npx skills add https://github.com/arthur-debert/dodot --skill using-dodot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you deploy, inspect, update, and remove dotfiles managed by dodot without breaking your live configuration or guessing which files are active.

Core Features & Use Cases

  • Deploy and synchronize packs: Use dodot up to create symlinks, register shell snippets, add bin directories to PATH, and run provisioning steps when needed.
  • Inspect live state: Use dodot status and probe commands to see what is deployed, what is pending, and whether a provisioning file is out of date.
  • Manage existing config: Add new files into a pack, adopt live configs into dodot, create pack scaffolds, or undo deployments cleanly with dodot down.
  • Use case: A developer pulls a dotfiles repo, wants to confirm which packs are active, add a new shell alias file, and redeploy only the affected pack.

Quick Start

Ask me to review your dodot packs, explain what will be deployed, and guide you through the safest status, up, down, add, or adopt command for your specific dotfiles change.

Frequently Asked Questions about using-dodot

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

FAQPage Schema
How do I deploy dotfiles using symlinks and shell integration without breaking my current setup?

Manage dotfiles deployments by running `dodot up` to create symlinks, register shell snippets, and add PATH directories. Inspect live filesystem state first with `dodot status` to see what is deployed and what is pending before applying changes.

What is the best way to check which dotfile packs are currently active on my system?

Checking which dotfile packs are active requires using `dodot status` and probe commands. These inspect the live filesystem state to show exactly what is deployed, what is pending, and whether any provisioning sentinels are out of date.

How do I add a new shell alias file to an existing dotfiles pack?

Adding a new shell alias file to an existing dotfiles pack uses the `dodot add` command. This integrates the new configuration file into the pack so you can redeploy only the affected pack with `dodot up`.

Can I adopt existing live configuration files into a dodot managed repository?

Yes, you can adopt existing live configuration files into a dodot managed repository using the `dodot adopt` command. This brings live configs into your dotfiles packs without breaking your current environment setup.

How do I cleanly undo a dotfiles deployment and remove symlinks?

To cleanly undo a dotfiles deployment and remove symlinks, use the `dodot down` command. This reverses the deployment by removing symlinks, unregistering shell sources, and cleaning up provisioning sentinels safely.

When should I not use automated dotfiles provisioning for shell configurations?

You should avoid automated dotfiles provisioning when your configuration repository lacks correct pack discovery rules or when provisioning sentinels are out of date. Always run `dodot status` to verify live filesystem state before executing `dodot up`.