chezmoi-update

Included with Lifetime

$97 forever

This skill should be used when the user asks to "update chezmoi", "sync dotfiles", "match live state", "match repo state", "chezmoi re-add", "chezmoi diff fix", "chezmoi apply", or mentions chezmoi source/live discrepancies, divergence between dotfiles repo and filesystem, or wants to reconcile chezmoi state in either direction.

Code Review

What this skill does


# Chezmoi Update — Syncing Source and Live State

## Principle: Live is Truth

The live filesystem is always the source of truth. The chezmoi source (repo) is a
**snapshot** of live state. All config files are plain files — no modify templates.

## Workflow

1. Run `chezmoi diff` to identify divergence
2. Classify each file by source filename
3. Sync using the correct method
4. Verify with `chezmoi diff` — expect empty output

## Classification

```bash
chezmoi source-path ~/.example/config.json
```

| Source filename pattern        | Type       | Sync method            |
| ------------------------------ | ---------- | ---------------------- |
| `*.tmpl`                       | Template   | Edit template directly |
| Plain file (no special prefix) | Plain file | `chezmoi re-add`       |

Also check for **permission diffs** (`old mode`/`new mode` in diff output):

- Mode `100600` = private (needs `private_` in filename)
- Mode `100644` = normal (no `private_` prefix)

## Live-to-Repo Sync (most common)

Since live is truth, the typical operation is capturing live state back to source:

```bash
chezmoi re-add ~/.example/config.json
```

Verify immediately with `chezmoi diff` — expect empty output.

## Repo-to-Live Sync

Only use when the source was intentionally edited (e.g., a bug fix in a config):

```bash
chezmoi apply ~/.example/config.json          # specific file
chezmoi apply --force ~/.example/config.json  # if chezmoi warns about changes
```

## Verification

After any sync operation:

1. `chezmoi diff <path>` — expect empty output for each synced file
2. If diff persists, compare: `chezmoi cat <path>` vs `cat <path>`
3. For source repo changes, review `git diff` in the dotfiles directory

## Anti-Patterns

- **Never use modify templates.** They create a fake SOT that drifts from reality and
  prevent `chezmoi re-add` from working.
- **Never assume `re-add` succeeded without verifying.** Always check `chezmoi diff` after.
- **Never apply without checking direction.** Confirm that source is intentionally ahead
  of live before overwriting live state.

Files: 1

Size: 2.4 KB

Complexity: 8/100

Category: Code Review

Source: https://github.com/shepherdjerred/monorepo/tree/main/packages/dotfiles/dot_agents/skills/chezmoi-update

Related in Code Review

gstack

Included

Fast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.

Code Reviewscripts

interview-master

Included

This skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.

Code Reviewscripts

fix-issue

Included

Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.

Code Reviewscripts

sf-apex

Included

Generates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.

Code Reviewscripts

swift-development

Included

Comprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.

Code Reviewscripts