OpenParable
Skip to content
← Back to skills

Cleanup Code Inspections

Development
cleanup-code-inspections

Cleanup Code Inspections is an Agent Skill for development published in the flutter/flutter-intellij repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Reduce technical debt and improve code quality by systematically resolving static analysis warnings.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/flutter/flutter-intellij/blob/HEAD/.agents/skills/cleanup-code-inspections/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cleanup-code-inspections, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Skill: Code Inspection & Cleanup

You are tasked with reducing technical debt and improving code quality by systematically resolving static analysis warnings.

Objective

Reduce technical debt and improve code quality by systematically resolving static analysis warnings.

Workflow Instructions

1. Baseline

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

2. Run Inspection

  • Execute Analyze > Inspect Code... on the project (or a specific module) using the "Default" profile.

3. Prioritize

  • Focus first on "Probable bugs", "Performance", and "Memory" categories.

4. Refactor

  • Apply quick-fixes for obvious issues (e.g., "Result of method call ignored", "String concatenation in loop").

5. Suppress

  • Explicitly suppress false positives with a comment and reason (e.g., //noinspection [ID] - [Reason]).

6. Verify

  • Run ./gradlew testClasses to ensure safe refactoring.
  • Run ./gradlew test and ./gradlew verifyPlugin to ensure no regressions.
  • Re-run analysis to ensure the "Yellow code" count has decreased and no regressions were introduced.

7. Report & Review

  • Summarize the inspections resolved.
  • 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 changes closely.
  • Do not commit or push.
  • Provide a suggested Git commit message (e.g., "Cleanup: Resolve static analysis warnings in [Module]").