CtrlK
BlogDocsLog inGet started
Tessl Logo

android-tooling

Configure static analysis with Detekt, Ktlint, and Android Lint for CI/CD quality gates. Use when adding lint rules, configuring code quality checks, or setting up analysis as a CI gate.

69

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Android Tooling Standards

Priority: P1

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
Commit

611f52a

Last updated
Created

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.

Claim skill