Coding Style Conventions

Name: Coding Style Conventions
Availability: InStock
Author: bryantchi

Enforce Kotlin coding style and linting standards for Android projects.

9|1|Updated Jan 26, 2026

Search Tags:#code review #linting #coding style #kotlin #ktlint #detekt #android development

Ready to run

npx skills add https://github.com/BryantChi/Android-Skills --skill coding-style-conventions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Coding Style Conventions
Source: https://github.com/BryantChi/Android-Skills/tree/main/coding_style_conventions
Command: npx skills add https://github.com/BryantChi/Android-Skills --skill coding-style-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps maintain high code quality and consistency across your Android projects by providing clear guidelines for Kotlin coding style, linting configurations, and code review standards.

Core Features & Use Cases

Standardized Naming: Ensures consistent naming conventions for classes, functions, variables, and more.
Linting & Formatting: Integrates with Detekt and Ktlint to automatically check and format code according to best practices.
Code Review: Provides a checklist to streamline the code review process, focusing on style and structural integrity.
Use Case: When starting a new Android project or refactoring an existing one, use this Skill to establish and enforce a professional coding standard.

Quick Start

Use the coding style conventions skill to check the naming of this Kotlin code snippet.

Frequently Asked Questions about Coding Style Conventions

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

FAQPage Schema

How do I enforce Kotlin coding style conventions in an Android project?▼

You can enforce Kotlin coding style by integrating Detekt and Ktlint to automatically check and format code, establishing standardized naming rules for classes and functions, and applying a comprehensive code review checklist to maintain structural integrity.

What is the best way to set up Detekt and Ktlint for a new Android project?▼

To set up Detekt and Ktlint for a new Android project, you configure the linters to automatically check formatting against best practices, define standardized naming conventions, and establish a code review checklist to bootstrap a professional coding standard.

Can I use these coding style rules to modernize a legacy Android codebase?▼

Yes, you can use these coding style rules to modernize a legacy Android project by applying standardized naming conventions, configuring Detekt and Ktlint for automated linting, and using the provided code review checklist to systematically improve structural integrity.

Does this Kotlin code review checklist cover both naming rules and structural integrity?▼

Yes, the Kotlin code review checklist covers both standardized naming conventions for variables and functions, as well as structural integrity checks, streamlining the review process for Android development projects.

Why do I need both Detekt and Ktlint for Android development code quality?▼

You need both Detekt and Ktlint because they work together to enforce Kotlin coding style: Ktlint handles code formatting, while Detekt performs static code analysis to enforce naming rules and code review standards for comprehensive Android project quality.