reload-ghengis

Force-sync the ghengis-skills plugin from GitHub and update local cache.

6|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/Kgan01/ghengis-skills --skill reload-ghengis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reload-ghengis
Source: https://github.com/Kgan01/ghengis-skills/tree/main/plugins/ghengis-skills/skills/reload-ghengis
Command: npx skills add https://github.com/Kgan01/ghengis-skills --skill reload-ghengis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill bypasses Claude Code's plugin update caching by forcing a refresh of the ghengis-skills plugin from GitHub, ensuring you’re always on the latest version.

Core Features & Use Cases

  • Bootstrap or locate the ghengis-skills marketplace clone and synchronize it with origin/master.
  • Read the new version from plugin.json and cache the fresh plugin under the new version.
  • Update installed_plugins.json to point to the new cached version and guide activation via Claude Code.

Quick Start

Invoke the reload-ghengis skill to force-sync the ghengis-skills plugin from GitHub.

Frequently Asked Questions about reload-ghengis

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

FAQPage Schema
How do I force-refresh a Claude Code plugin to the latest version?

To force-refresh a Claude Code plugin, you can use a skill that force-syncs the plugin from GitHub, bypassing the local update cache. This fetches the latest origin/master, reads the new version from plugin.json, and copies the fresh files into your local cache.

Why does my Claude Code plugin update cache show an old version?

Claude Code's plugin update caching can retain outdated versions when the marketplace clone is missing or stale. Bypassing this cache by resetting the clone and force-syncing from origin/master ensures the latest plugin version is read and cached locally.

How do I sync my installed Claude Code plugins with the latest GitHub release?

You can sync installed plugins with the latest GitHub release by force-fetching origin/master, caching the fresh plugin under its new version, and updating installed_plugins.json with the new version, cache path, and Git SHA for traceability.

How does GitHub versioning work when updating cached plugins in Claude Code?

GitHub versioning for cached plugins works by reading the new version from plugin.json after fetching origin/master. The plugin is copied to a local cache, and installed_plugins.json is updated with the version, cache path, and Git SHA to enable seamless activation.

Can I activate a force-refreshed plugin after bypassing the update cache?

Yes, after force-refreshing the plugin and updating installed_plugins.json with the new version and Git SHA, you can seamlessly activate the fresh plugin using the /reload-plugins command in Claude Code.

What happens if the marketplace clone is missing during a plugin update?

If the marketplace clone is missing during a plugin update, the force-refresh skill will bootstrap or locate the clone, synchronize it with origin/master, and cache the fresh plugin locally to ensure you are on the latest version.