footing-update

Synchronizes a local Footing pack with the GitHub repository using three-way SHA reconciliation.

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/MilUX-Ltd/footing --skill footing-update-milux-ltd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: footing-update
Source: https://github.com/MilUX-Ltd/footing/tree/main/footing/template/Skills/meta-skills/footing-update
Command: npx skills add https://github.com/MilUX-Ltd/footing --skill footing-update-milux-ltd

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about footing-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update my Footing pack to the latest version?▼

Run /footing-update or say "update Footing". The skill fetches the file tree from the public GitHub repo, compares SHAs against your local files, and applies new and upstream-only changes after showing you a summary.

Will updating Footing overwrite my personalized files?▼

No. Install-built files like your operator profile, Brand.md, Strategy.md, and CLAUDE.md are protected and never touched. Files you have edited locally are only overwritten if you explicitly choose "take theirs" on a conflict.

How does the skill detect which files changed?▼

It compares three git-blob SHAs per file: the SHA stored in .footing/config.yml from the last pull, the current remote SHA from the GitHub tree API, and a locally recomputed SHA via git hash-object or a Python equivalent.

Does footing-update require GitHub authentication?▼

No. The repository is public, so the skill uses unauthenticated GitHub API calls. The tradeoff is a 60-requests-per-hour rate limit; if hit mid-run, partial progress is saved and you can retry later.

What happens if a file has both local edits and upstream changes?▼

That file is flagged as a conflict. The skill shows a diff summary and offers three options per file: take theirs, keep mine, or merge, where a concrete merged version is proposed for your confirmation before writing.

What are the limitations of footing-update?▼

It never deletes files removed upstream, does not re-run onboarding, and falls back to additive-only behavior if neither git nor Python is available to compute SHAs. Protected install-built files require a separate manual refresh.