package-remove

Remove a Unity package from manifest.json and trigger package resolution.

3.8k|349|Updated Apr 2, 2025
One-click install
npx skills add https://github.com/IvanMurzak/Unity-MCP --skill package-remove-ivanmurzak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: package-remove
Source: https://github.com/IvanMurzak/Unity-MCP/tree/main/Unity-MCP-Plugin/.claude/skills/package-remove
Command: npx skills add https://github.com/IvanMurzak/Unity-MCP --skill package-remove-ivanmurzak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Removing a Unity package from the project manifest and triggering package resolution to recover a clean project state. It enforces constraints like built-in packages or dependencies of other installed packages cannot be removed.

Core Features & Use Cases

  • Remove a package from the manifest.json and trigger package resolution.
  • Prevent deletion of built-in packages or packages required by other installed packages.
  • Use case: Clean up unused packages after refactoring or to reduce project bloat.

Quick Start

Run the tool with a JSON input containing the packageId to uninstall the target package.

Frequently Asked Questions about package-remove

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

FAQPage Schema
How do I safely remove a Unity package from the manifest?

To remove a Unity package safely, the tool deletes the package entry from the manifest and triggers package resolution. It enforces constraints by preventing the removal of built-in packages or dependencies required by other installed packages.

Can I delete a Unity package that is a dependency of another installed package?

No, you cannot delete a Unity package that is a dependency of another installed package. The tool enforces this constraint to prevent breaking project references and reports the blocked removal result after the domain reload.

What happens when I remove unused Unity packages from my project?

When you remove unused Unity packages, the tool updates the manifest and triggers package resolution to recover a clean project state. This helps reduce project bloat and resolve conflicts after refactoring.

Why does removing a Unity package trigger a domain reload?

Removing a Unity package triggers a domain reload because the tool initiates package resolution to update the project environment. The tool reports the final removal results after this domain reload completes successfully.

What is the best way to clean up unused Unity packages after refactoring?

The best way to clean up unused Unity packages after refactoring is to use a tool that removes the package from the manifest and triggers resolution. This ensures a clean project state while preventing the deletion of built-in packages.