flutter/flutter-intellij · Archived

cleanup-unused-assets

Reduce plugin size by scanning resources/icons and removing unreferenced assets.

First seen Jul 20, 2026

Installation

$ npx skills add flutter/flutter-intellij --skill cleanup-unused-assets

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from flutter/flutter-intellij · top by installs.

npx skills add flutter/flutter-intellij

Browse all from flutter/flutter-intellij

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2.0K
License LICENSE
Default branch main
Open issues 647
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,511 B
  • docs SUMMARY.md 109 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 6 installs

SKILL.md

Skill: Unused Asset Cleanup

You are tasked with reducing plugin size by removing unused icons, images, and resources.

Objective

Reduce plugin size by removing unused icons, images, and resources.

Workflow Instructions

1. Baseline

  • Run ./gradlew test and ./gradlew verifyPlugin to ensure the project is stable.

2. Scan Assets

  • List all files in resources/icons and other asset directories.

3. Search Usages

  • Check if each asset is referenced in code or plugin.xml.

4. Remove

  • Delete assets with zero references.

5. Verify

  • Run ./gradlew buildPlugin and check that the plugin still loads correctly without missing resource exceptions.
  • Run ./gradlew testClasses, ./gradlew test and ./gradlew verifyPlugin to ensure no regressions.
  • Suggest manual test steps: Check code changes made and write test steps for a user to execute that trigger changed code paths. If needed, add logging statements to verify code paths successfully run.

6. Report & Review

  • Summarize assets removed.
  • Test Location: Explicitly state where in the IDE user should go to test changed functionality (e.g., "Go to Preferences > Languages & Frameworks > Flutter").
  • Action: Ask user to review deletions closely.
  • Do not commit or push.
  • Provide a suggested Git commit message (e.g., "Cleanup: Remove unused icon [Icon Name]").