What problem does it solve? A committed Fux search index goes stale the moment content changes and conflicts when two branches touch the same shard. This Skill keeps the index current by wiring git hooks, running a URL freshness daemon, checking drift, and resolving merge conflicts in .fux/index without hand-editing JSONL shards. ## Core Features & Use Cases - Git hook management: Install, inspect, and uninstall post-commit, post-merge, and post-checkout hooks plus the fux-merge-index merge driver, with JSON status output that never installs anything. - Freshness daemon: Start, monitor, and stop a background process that re-fetches listed URLs on a timer and writes the index directly. - Drift detection and CI gating: Run fux ingest --check for read-only drift reports and set up CI that proves the committed index matches the content. - Merge conflict resolution: Resolve .fux/index shard conflicts by taking one side whole, then re-deriving the index with fux ingest. - Use Case: A teammate reports a merge conflict in .fux/index after merging two branches. You check out one side of the conflicted shards, complete the merge, run fux ingest, and commit the regenerated index. ## Quick Start Ask the agent to check whether the fux hooks are wired in this repository and report the JSON status.