skill-update-check

You can check for upstream changes and security regressions by running an automated repository comparison and security scanning process across repositories with skill files to identify and report potential updates or vulnerabilities.

The best way to audit skill repositories for untrusted modifications is to analyze differences in skills against their source repositories using automated security scanning to identify potential issues introduced by upstream changes.

Yes, you need the gh dependency installed to automate skill repository security scanning, as the scripts use it to access repositories and verify if imported skills have updated commits on their source.

No, the automated skill update process does not apply changes directly. It identifies, reports, and guides on updating skills only after manual review to ensure repository safety and currentness.