auto-updater

Skill updates are secured by checking for newer immutable commit SHAs and generating full diffs before any changes are applied. This process requires explicit human approval to prevent silent upgrades and ensure safe update management.

Security gating flags high-risk surface-area changes like hooks, MCP config, and tool permission escalation during skill updates. It requires explicit human approval and runs skills-qa re-verification on the new version before any install-time replacement.

Commit SHA pinning locks installed legal skills to specific immutable commits. When checking for updates, the system compares against these pinned SHAs to detect newer versions and generate accurate diffs for review before applying changes.

Yes, the update process generates full diffs of all changes before anything is applied. You review the complete diff and must give explicit approval before any install-time replacement occurs, ensuring full visibility into skill updates.

Use a diff review workflow when a registry-sync agent checks for newer skill versions or when freshness windows have passed. This ensures trust-sensitive changes like hooks and MCP config are flagged and re-verified before any installation occurs.

Yes, the update verification process can be invoked by a registry-sync agent to keep community legal skills current. The agent triggers diff generation, security gating, and explicit approval requirements before any install-time replacement occurs.