cleanup-code-inspections

cleanup-code-inspections is a skill for Claude Code, Codex from flutter/flutter-intellij. It costs 19 tokens per session (390 once invoked), scanned A, original, BSD-3-Clause.

A guided process for finding and fixing warnings from static code analysis, which checks source code for likely bugs and maintainability problems.

In plain words
What is it for?
Use it to inspect a Gradle project, fix likely bugs and performance or memory issues, document intentional exceptions, and rerun tests and inspections.
Why use it?
It turns a long list of warnings into an ordered cleanup process and checks that the changes do not break the project.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/flutter/flutter-intellij/cleanup-code-inspections
Any agent
npx skills add flutter/flutter-intellij --skill cleanup-code-inspections
Clone the repo
git clone --depth 1 https://github.com/flutter/flutter-intellij

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for cleanup-code-inspections

README.md
[![agentmods](https://agentmods.dev/badge/skills/flutter/flutter-intellij/cleanup-code-inspections.svg)](https://agentmods.dev/skills/flutter/flutter-intellij/cleanup-code-inspections)
Your own site
<a href="https://agentmods.dev/skills/flutter/flutter-intellij/cleanup-code-inspections"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/cleanup-code-inspections.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 390 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.00390
Opus 5 $0.00010 $0.00195
Sonnet 5 $0.00004 $0.00078
Haiku 4.5 $0.00002 $0.00039

Measured 4d ago against content hash 7c318a431117, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cleanup-code-inspections scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/cleanup-code-inspections/SKILL.md · 41 lines

What it actually says

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]").
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 41 lines · 19 tokens per session scan A 7c318a431117

Subscribe to this mod's changes

cleanup-code-inspections is a skill published in the GitHub repository flutter/flutter-intellij (2,013 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 19 tokens to every session and 390 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.