auto-updater

Check installed community skills for updates and apply them only after diff review and approval.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/tk1cntt/PhapChe --skill auto-updater-tk1cntt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-updater
Source: https://github.com/tk1cntt/PhapChe/tree/main/docs/claude-for-legal-main/legal-builder-hub/skills/auto-updater
Command: npx skills add https://github.com/tk1cntt/PhapChe --skill auto-updater-tk1cntt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Community skills installed in a legal environment can change upstream, and blindly updating code that runs with privileged access is a security risk. This Skill detects available updates, shows exactly what changed, and blocks any update from being applied without explicit human approval. ## Core Features & Use Cases - SHA-pinned update checks: Compares each installed skill's pinned commit SHA against the source registry, ignoring mutable tags and branches. - Trust review and diff display: Shows full unified diffs and flags changes to hooks, MCP server configs, tool permissions, network calls, and the skill's stated purpose. - Security re-scan and freshness checks: Re-runs a skills-qa scan on the new version in a read-only subagent and verifies whether bundled reference material is still within its freshness window. - Backup and rollback: Backs up the old version before applying an update and supports restoring it with a rollback command. - Use Case: A legal team runs the updater weekly to see whether any installed skills have new commits, reviews the diffs for permission changes, and approves only the updates that pass the security re-scan. ## Quick Start Ask the assistant to check for updates to your installed skills and show the diffs before applying anything.

Frequently Asked Questions about auto-updater

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

FAQPage Schema
How do I check installed Claude skills for updates?

Invoke the auto-updater skill, which loads your installed skills list from the hub config, fetches each source registry's current commit SHA, and compares it to the SHA pinned at install time. Any difference is reported as an available update with a full diff.

Can skill updates be applied automatically without approval?

No. The skill has no auto-apply mode by design. Every update shows a full diff and trust review, and changes to hooks, MCP configs, or tool permissions always force a human-approval prompt regardless of scan results.

Why does the updater use commit SHAs instead of version tags?

Tags and branch heads are mutable and can be retroactively rewritten by a publisher, while commit SHAs are immutable. Pinning SHAs ensures the code you reviewed is exactly the code that gets installed.

What happens if an updated skill fails the security scan?

If the new version triggers a REFUSE-tier finding such as exfiltration or credential theft, the update is refused with no apply-anyway option. You can roll back or uninstall, but there is no override flag.

How do I roll back a skill update that broke something?

Run the updater with the rollback flag and the skill name. The old version was backed up before the update was applied, so rollback restores it from that backup directory.

Does the updater manage manually installed skills?

No. It only updates skills installed through the hub, since those have pinned SHAs and install logs. Manually placed skills remain the user's responsibility to manage.