mucc-update

Update MUCC plugins and skill symlinks via non-destructive git pulls.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill mucc-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mucc-update
Source: https://github.com/MaxGiu67/plugin-MUCC/tree/main/dev-methodology/skills/mucc-update
Command: npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill mucc-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps local MUCC plugin repositories synchronized and reduces broken or outdated skill symlinks in Claude Code environments by automating repository updates, symlink refreshes, changelog reporting, and tool checks so users avoid manual git operations and missing skill detections.

Core Features & Use Cases

  • Repository detection: Locates the MUCC repo by resolving installed skill symlinks or prompting for the path if none are found.
  • Safe update workflow: Performs a non-destructive git pull with clear error reporting and no automatic destructive merges or resets.
  • Skill symlink management: Reads mucc-plugins.json and creates, updates, or skips symlinks for plugin skills while preserving safety checks.
  • Changelog & tool verification: Shows commit diffs and CHANGELOG.md excerpts and lists missing external tools, offering an optional guided install prompt.
  • Use case: Ideal for developers or maintainers who install MUCC locally and need a repeatable, safe way to refresh plugins after upstream changes.

Quick Start

Run the mucc-update routine to pull the latest repository, refresh skill symlinks according to mucc-plugins.json, and display changelog and missing tools.

Frequently Asked Questions about mucc-update

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

FAQPage Schema
How do I update MUCC plugins and refresh skill symlinks in Claude Code?

To update MUCC plugins and refresh skill symlinks, run the mucc-update routine to perform a non-destructive git pull, parse mucc-plugins.json, and automatically synchronize symlinks for your local Claude Code installation.

What is the safest way to pull upstream changes for a local Claude Code plugin repository?

The safest way to pull upstream changes is using a non-destructive fast-forward git pull workflow that preserves local modifications, reports errors clearly, and avoids automatic destructive merges or resets.

Can I automatically detect the repository path for MUCC plugins without manual input?

Yes, you can detect the MUCC repository path automatically by resolving installed skill symlinks, which allows the update tool to locate the target directory without requiring manual user input.

How does changelog reporting and external tool verification work after updating plugins?

Changelog reporting and external tool verification work by displaying commit diffs and CHANGELOG.md excerpts, then listing missing quality and security tools while offering an optional guided installation prompt.

What happens to existing local changes when synchronizing MUCC skill symlinks?

When synchronizing MUCC skill symlinks, existing local changes are preserved because the system applies safety checks and skips symlinks or pulls that would forcibly reset user modifications.

Do I need to manually install missing external tools before running a plugin update?

No, you do not need to manually install missing external tools beforehand because the update process inspects tool availability and provides an optional guided install prompt after reporting missing dependencies.