cleanup-code-inspections Skill
Reduce technical debt and improve code quality by systematically resolving static analysis warnings. Published by flutter in flutter-intellij.
Decision snapshot
Is this a fit?
Testing, Data analysis, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
18 days ago · BSD-3-Clause license
No specific cautions were detected. Review the source and requested permissions before installing.
What is cleanup-code-inspections Skill?
Reduce technical debt and improve code quality by systematically resolving static analysis warnings. Published by flutter in flutter-intellij. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Data analysis
- Testing use cases
- Data analysis use cases
Declared skill metadata
- Source file: .agents/skills/cleanup-code-inspections/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use cleanup-code-inspections Skill
- Use it for testing.
- Use it for data analysis.
Built with
Editorial notes
Source
- Creator: flutter
- Repository: flutter/flutter-intellij
- Skill file: .agents/skills/cleanup-code-inspections/SKILL.md
What it does
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
Skill instructions
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 t
Verified compatibility and discovery
Frequently asked questions
What is cleanup-code-inspections?
cleanup-code-inspections is a open-source AI agent skill with Copy skill directory. Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
Who is cleanup-code-inspections best for?
cleanup-code-inspections is best for reusing agent instructions, scripts, and references, testing workflows, data analysis workflows.
How do I install cleanup-code-inspections?
Install or run cleanup-code-inspections using Copy skill directory. Check cleanup-code-inspections for the latest setup command.
Is cleanup-code-inspections actively maintained?
cleanup-code-inspections may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
