tether

Dotfiles Hooks Manager

Manage chezmoi-sync-reminder hook installation in ~/.claude/settings.json.

Claude Code only loads hooks from settings.json, not from plugin.json files. This command installs/uninstalls the chezmoi PostToolUse hook that reminds you to sync dotfile changes.

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

Actions

Action	Description
status	Show current installation state
install	Add chezmoi hook to settings.json
uninstall	Remove chezmoi hook from settings.json
restore	List available backups with numbers
restore latest	Restore most recent backup
restore <n>	Restore backup by number

Execution

Parse $ARGUMENTS and run the management script:

/usr/bin/env bash << 'HOOKS_SCRIPT_EOF'
PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/plugins/marketplaces/cc-skills/plugins/dotfiles-tools}"
ACTION="${ARGUMENTS:-status}"
bash "$PLUGIN_DIR/scripts/manage-hooks.sh" $ACTION
HOOKS_SCRIPT_EOF

Post-Action Reminder

After install/uninstall/restore operations:

IMPORTANT: Restart Claude Code session for changes to take effect.

The hooks are loaded at session start. Modifications to settings.json require a restart.

Examples

# Check current installation status
/dotfiles-tools:tether status

# Install the chezmoi sync reminder hook
/dotfiles-tools:tether install

# Uninstall hooks
/dotfiles-tools:tether uninstall

# List available backups
/dotfiles-tools:tether restore

# Restore most recent backup
/dotfiles-tools:tether restore latest

Troubleshooting

Issue	Cause	Solution
jq not found	jq not installed	brew install jq
Already installed	Hook already in settings	Run uninstall first to reinstall
Hooks not working	Session not restarted	Restart Claude Code session
Settings file not found	~/.claude/ doesn't exist	Create with mkdir -p ~/.claude
Invalid JSON	Corrupted settings.json	Use restore latest to recover from backup

Post-Execution Reflection

After this skill completes, check before closing:

1. Did the command succeed? — If not, fix the instruction or error table that caused the failure.
2. Did parameters or output change? — If the underlying tool's interface drifted, update Usage examples and Parameters table to match.
3. Was a workaround needed? — If you had to improvise (different flags, extra steps), update this SKILL.md so the next invocation doesn't need the same workaround.

Only update if the issue is real and reproducible — not speculative.