pull-codex-config

To safely pull a git repository update without losing local changes, this Skill clones missing repos or fast-forwards existing clean checkouts, stopping to report modified files instead of stashing or discarding work.

When syncing your Codex configuration with uncommitted changes, the process halts and reports the dirty files. It requires explicit user approval before proceeding and never silently stashes or resets your work.

To refresh local dot-codex skills and scripts, the Skill fast-forwards your existing clean checkout to the latest upstream version, keeping AGENTS rules and configuration aligned without overwriting uncommitted work.

Yes, this repository sync method requires a clean git worktree for fast-forwarding. It validates the Git remote and performs clean-worktree checks, only proceeding with dirty pulls after explicit user approval.

Yes, you can clone a missing Codex configuration repository automatically. The Skill detects if the local checkout is absent and safely clones the repository to establish your baseline configuration.

Your git pull fails on modified configuration files because this Skill enforces clean-worktree checks to preserve uncommitted changes. It stops the fast-forward and reports dirty files rather than silently overwriting them.