android-lint-fix

Fix Android lint, Kotlin compiler warnings, and Detekt violations rule by rule.

1|Updated Feb 28, 2026

Search Tags:#code quality #static analysis #warnings #android #kotlin #lint #detekt

Ready to run

npx skills add https://github.com/Binh230199/ai --skill android-lint-fix

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: android-lint-fix
Source: https://github.com/Binh230199/ai/tree/main/.github/skills/android-lint-fix
Command: npx skills add https://github.com/Binh230199/ai --skill android-lint-fix

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the risk and guesswork from fixing Android Lint, Kotlin compiler warnings, and Detekt violations in Android Kotlin and Java codebases.

Core Features & Use Cases

Rule-by-rule remediation: Groups findings by issue ID so each static analysis problem is fixed in isolation.
Safe verification workflow: Prioritizes severity, checks related issues, and validates that new warnings are not introduced.
Suppression guidance: Provides last-resort suppression patterns with required justification when a fix is not practical.
Use case: Ideal for cleaning up CI failures, IDE warnings, and pre-commit static analysis reports without causing cascading regressions.

Quick Start

Use this skill to review the provided lint report or code change and fix each Android static analysis issue one rule at a time.

Frequently Asked Questions about android-lint-fix

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix Android lint warnings and Detekt violations in a Kotlin codebase?▼

To fix Android lint warnings and Detekt violations, group findings by issue ID and apply per-rule remediation. This approach isolates each static analysis problem, applies minimal code changes, and verifies that no new warnings are introduced.

What is the best way to clear CI lint failures without causing regressions?▼

The best way to clear CI lint failures safely is to prioritize severity, fix issues rule-by-rule, and perform post-fix verification. This prevents cascading regressions while ensuring staged diffs and IDE diagnostics pass static analysis checks.

Can I suppress Kotlin compiler warnings when a practical code fix is not possible?▼

You can suppress Kotlin compiler warnings as a last resort. Suppression patterns require explicit justification when a practical fix is not feasible, ensuring static analysis rules are bypassed safely and transparently in the codebase.

Does rule-by-rule remediation work for staged diffs and pasted static analysis reports?▼

Rule-by-rule remediation works for staged diffs, IDE diagnostics, CI lint failures, and pasted reports. It processes Android Kotlin and Java codebases by isolating each issue ID for targeted, minimal code changes.

Why should I group static analysis findings by issue ID before fixing?▼

Grouping static analysis findings by issue ID fixes each problem in isolation. This method prioritizes severity, checks related issues, and validates post-fix verification to ensure minimal code changes without introducing new warnings.