Dotfiles Management Assistant

Expert assistant for managing mimikun's comprehensive cross-platform dotfiles repository. Specializes in chezmoi template management, multi-OS support, secret handling, and automated quality assurance workflows.

Overview

This skill provides guidance for working with a sophisticated dotfiles setup that supports Linux, Windows, and macOS environments. The repository uses modern tooling for configuration management, version control, and automated testing.

Core Technologies

**chezmoi**: Dotfiles management with Go templating and secret integration

**mise**: Tool version management and task automation

**aqua**: Lightweight CLI tool package manager

**lefthook**: Git hooks for quality assurance

**renovate**: Automated dependency updates

Instructions

1. Understanding Project Structure

When exploring this dotfiles repository:

Files prefixed with `dot_` become `.filename` in the home directory

Files with `.tmpl` extension are processed as chezmoi templates

Files prefixed with `private_` have restricted permissions (600)

Files prefixed with `executable_` are marked executable

**Key directories:**

`dot_config/nvim/` - Neovim configuration (Lua 5.1)

`dot_config/fish/` - Fish shell setup

`docs/design/` - Design philosophy documents

`scripts/` - Utility scripts (excluded from chezmoi)

`.github/` - CI/CD workflows

2. chezmoi Operations

**Primary workflows:**

```bash

View changes before applying

chezmoi diff

Apply dotfiles

chezmoi apply --verbose

Check current status

chezmoi status

Edit a template file

chezmoi edit <file>

Navigate to source directory

chezmoi cd

Test template rendering

chezmoi execute-template < template-file

Re-initialize from repository

chezmoi init --apply --verbose https://github.com/mimikun/dotfiles.git

```

**Always run `chezmoi diff` before `chezmoi apply` to review changes.**

3. Multi-OS Template Patterns

Use these patterns for OS detection in chezmoi templates:

```go-template

{{- $isWorkLinux := (and (eq .chezmoi.os "linux") (isExecutable "/usr/local/bin/this_is_work_pc")) -}}

{{- $isWorkWindows := (and (eq .chezmoi.os "windows") (isExecutable "C:\\Program Files\\Yt Env Checks\\this_is_work_pc.exe")) -}}

Windows-specific configuration

Linux-specific configuration

macOS-specific configuration

```

4. Secret Management

Handle secrets securely using chezmoi's secret integration:

```go-template

Work PC: Use Bitwarden CLI

Personal PC: Use static values from chezmoi data

```

**Never commit secrets directly to the repository.**

5. mise Task Management

Run common tasks using mise:

```bash

View all available tasks

mise tasks list

Run linting

mise tasks run lint

Run formatting

mise tasks run format

Clean temporary files

mise tasks run clean

Update dependencies

mise tasks run update

Create patch branch

mise tasks run patch:branch

Check tool installation

mise doctor

```

6. Development Standards

**Lua (Neovim configurations):**

Target Lua 5.1 for Neovim compatibility

Format with `stylua`

Lint with `selene`

Follow lazy.nvim plugin structure:

```lua

return {

"plugin/name",

dependencies = {},

opts = {},

config = function(_, opts)

-- Configuration

end,

}

```

**Bash scripts:**

```bash

#!/usr/bin/env bash

set -euo pipefail

Use chezmoi template variables

Windows-specific code

Unix-specific code

```

**PowerShell scripts:**

```powershell

#Requires -Version 5.1

[CmdletBinding()]

param()

Follow PSScriptAnalyzer standards

```

7. Quality Assurance

Run quality checks before committing:

```bash

Run all quality checks

make lint

Run formatting

make format

Manual pre-commit hook execution

lefthook run pre-commit

Install git hooks

lefthook install

```

**Individual linters:**

```bash

Lua

stylua --check .

selene .

JavaScript/TypeScript

npx prettier --check .

npx textlint docs/

Spell checking

npx cspell "**/*.md" "**/*.txt"

PowerShell

pwsh -Command "Invoke-ScriptAnalyzer -Path . -Recurse"

```

8. Feature Development Workflow

1. Create a patch branch: `make patch-branch`

2. Edit template files: `chezmoi edit <file>`

3. Test changes: `chezmoi diff`

4. Apply locally: `chezmoi apply`

5. Run quality checks: `make lint`

6. Commit using conventional commits format:

```

<body>

```

Types: `feat`, `fix`, `docs`, `style`, `refactor`, `test`, `chore`

9. aqua Package Management

Manage CLI tools with aqua:

```bash

Install packages from aqua.yaml

aqua install

Update packages

aqua update

Add new package

aqua generate <package-name>

Verify package installation

aqua which <tool>

```

10. Branch Management

```bash

Create new patch branch

make patch-branch

Switch to master

make switch-master

Delete current branch

make delete-branch

Morning routine (fetch, pull, cleanup)

make morning-routine

```

Best Practices

1. **Always use chezmoi variables** - Never hardcode paths or OS-specific values

2. **Test templates thoroughly** - Use `chezmoi diff` and `chezmoi execute-template`

3. **Validate on target OS** - Test multi-OS templates on each platform

4. **Profile performance** - Keep shell startup time minimal with lazy loading

5. **Review security** - Never commit secrets, validate executable paths

6. **Use mise tasks** - Leverage task automation for complex operations

7. **Maintain consistency** - Follow existing patterns for file naming and structure

Common Pitfalls

❌ Hardcoding paths instead of using chezmoi variables

❌ Committing secrets directly to repository

❌ Skipping `chezmoi diff` before apply

❌ Adding heavy operations to shell startup

❌ Breaking cross-platform compatibility

Tool-Specific Documentation

**Neovim**: See `dot_config/nvim/CLAUDE.md` for AI guidance and `docs/design/nvim.md` for design philosophy

**chezmoi Templates**: Reference OS detection patterns above

**PowerShell**: Follow PSScriptAnalyzer standards

**Fish Shell**: Use global configuration patterns

Monitoring & Maintenance

```bash

Check mise tools

mise doctor

Verify aqua packages

aqua which <tool>

Test template rendering

chezmoi execute-template < template-file

```

Renovate automatically creates PRs for dependency updates. Review and test before merging.

---

**Remember:** This is a living configuration optimized for cross-platform compatibility and performance. Always test changes across target operating systems and maintain security best practices.

Dotfiles Management Assistant

Dotfiles Management Assistant

Overview

Core Technologies

Instructions

1. Understanding Project Structure

2. chezmoi Operations

View changes before applying

Apply dotfiles

Check current status

Edit a template file

Navigate to source directory

Test template rendering

Re-initialize from repository

3. Multi-OS Template Patterns

Windows-specific configuration

Linux-specific configuration

macOS-specific configuration

4. Secret Management

Work PC: Use Bitwarden CLI

Personal PC: Use static values from chezmoi data

5. mise Task Management

View all available tasks

Run linting

Run formatting

Clean temporary files

Update dependencies

Create patch branch

Check tool installation

6. Development Standards

Use chezmoi template variables

Windows-specific code

Unix-specific code

Follow PSScriptAnalyzer standards

7. Quality Assurance

Run all quality checks

Run formatting

Manual pre-commit hook execution

Install git hooks

Lua

JavaScript/TypeScript

Spell checking

PowerShell

8. Feature Development Workflow

9. aqua Package Management

Install packages from aqua.yaml

Update packages

Add new package

Verify package installation

10. Branch Management

Create new patch branch

Switch to master

Delete current branch

Morning routine (fetch, pull, cleanup)

Best Practices

Common Pitfalls

Tool-Specific Documentation

Monitoring & Maintenance

Check mise tools

Verify aqua packages

Test template rendering

Reviews (0)