CtrlK
BlogDocsLog inGet started
Tessl Logo

android-tooling

Configure Android static analysis with Detekt, Ktlint, and Android Lint for CI/CD quality gates. Use for Android-specific lint and quality tooling; defer generic Java Checkstyle, SonarQube, and standalone CI configuration.

69

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Android Tooling Standards

Priority: P1 (HIGH)

Implementation Guidelines

Static Analysis

  • Detekt: Enforce code complexity rules (LongMethod, LargeClass). Fail build on high complexity.
  • Ktlint: Enforce formatting style (Indent, Spacing). Use jlleitschuh plugin.
  • Android Lint: Treat warnings as errors in CI (abortOnError = true).

CI Gates

  • Pre-commit: Run lightweight checks (formatting) locally.
  • Pipeline: Run full checks (Detekt + Lint + Unit Tests) on Pull Request.

Anti-Patterns

  • No @Suppress in Production: Fix Detekt/lint violation at source.
  • No Manual Formatting: Let Ktlint handle it — configure auto-format on save in IDE.

References

  • Configuration
Repository
HoangNguyen0403/agent-skills-standard
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.