flutter/flutter-intellij · Archived

audit-dependencies

Optimize plugin size and security by removing unused dependencies and updating outdated libraries.

First seen Jul 20, 2026

Installation

$ npx skills add flutter/flutter-intellij --skill audit-dependencies

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,900 B
  • docs SUMMARY.md 124 B

History

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

SKILL.md

Skill: Dependency & Library Audit

You are tasked with optimizing plugin size and security by removing unused dependencies and updating outdated libraries.

Objective

Optimize plugin size and security by removing unused dependencies and updating outdated libraries.

Workflow Instructions

1. Baseline

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

2. Audit build.gradle

  • Review dependencies {} block. Identify libraries that might no longer be used.

3. Check plugin.xml

  • Ensure all <depends> tags match actual API usage.

4. Update Versions

  • Check for newer stable versions of third-party libraries.

5. Remove Unused

  • Delete any local .jar files in lib/ that are not referenced or can be replaced by Maven coordinates.

6. Verify

  • Run ./gradlew buildPlugin and check the distribution size. Ensure the plugin still loads and functions correctly.
  • Run ./gradlew testClasses, ./gradlew test, and ./gradlew verifyPlugin to ensure no checking or runtime issues were introduced.
  • Suggest manual test steps: Check the code changes made and write test steps for a user to execute that will trigger the code paths that have changed. If needed, add logging statements to verify that the code paths have successfully run.

7. Report & Review

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