What problem does it solve? Keeping a locally installed Footing knowledge pack current with upstream changes is risky: naive updates either ignore files the user has personalized or blindly overwrite their edits. This skill reconciles the local vault against the public GitHub repo so users get upstream improvements without losing their own work. ## Core Features & Use Cases - Three-way SHA reconciliation: Compares the last-pulled SHA, the current GitHub blob SHA, and the locally computed git-blob SHA for every shipping file, categorizing each as new, in-sync, upstream-only, local-only, converged, or conflicted. - Self-upgrading skill: Checks whether its own SKILL.md has changed upstream and offers to upgrade itself first, so future behavior changes propagate automatically. - Protected file handling: Never touches install-built files (operator profile, Brand, Strategy, CLAUDE.md, etc.) that were personalized during setup. - Conflict resolution UX: Surfaces conflicts one-by-one with take-theirs / keep-mine / merge options, and proposes concrete merged versions for confirmation. - Use Case: A user says "check for Footing updates" and the skill reports 3 new files, 5 safe upstream updates, and 1 conflict, applies the approved changes, updates the SHA tracking in .footing/config.yml, and reports what changed. ## Quick Start Say "update Footing" or "pull the latest from Footing" to fetch the newest pack content from GitHub and reconcile it with your local edits.