bill-kotlin-code-review-architecture

Analyze Kotlin module boundaries and DI scopes for architectural correctness.

13|1|Updated Mar 16, 2026

Search Tags:#architecture #kotlin #code-review #di #module-boundaries #dependency-direction #architecture-consistency

Ready to run

npx skills add https://github.com/Sermilion/skill-bill --skill bill-kotlin-code-review-architecture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bill-kotlin-code-review-architecture
Source: https://github.com/Sermilion/skill-bill/tree/main/platform-packs/kotlin/code-review/bill-kotlin-code-review-architecture
Command: npx skills add https://github.com/Sermilion/skill-bill --skill bill-kotlin-code-review-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides structured, expert guidance to verify and enforce architectural boundaries, DI scope correctness, and source-of-truth consistency in Kotlin projects, enabling teams to align on a robust architectural stance.

Core Features & Use Cases

Architectural review of module boundaries, dependency direction, and DI lifecycles
Detect and resolve source-of-truth inconsistencies across layers
Provide actionable remediation guidance and guardrails for Kotlin codebases
Real-world use case: when a change touches multiple layers, this skill maps impact and suggests refactors

Quick Start

Identify current Kotlin module boundaries and DI scopes, and propose concrete adjustments to improve architectural integrity.

Frequently Asked Questions about bill-kotlin-code-review-architecture

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

FAQPage Schema

How do I review Kotlin architecture for module boundaries and dependency direction?▼

Reviewing Kotlin architecture involves analyzing module boundaries and dependency direction to enforce structural integrity. This process evaluates multi-module projects to ensure layers remain decoupled, verifying that dependencies point correctly and identifying source-of-truth inconsistencies for actionable remediation.

What is DI scope correctness and how does it affect Kotlin multi-module projects?▼

DI scope correctness ensures dependency injection lifecycles align with module boundaries in Kotlin projects. Correct scoping prevents memory leaks and unauthorized cross-layer access, maintaining source-of-truth consistency across application and library modules while providing actionable remediation guidance.

How do I fix source-of-truth inconsistencies across Kotlin architectural layers?▼

Fix source-of-truth inconsistencies by mapping the impact of changes across multiple layers and suggesting refactors. This analysis detects structural mismatches within Kotlin codebases, providing guardrails and non-regression checks to realign data ownership and enforce architectural boundaries.

Can I use this architectural review for both library and application Kotlin modules?▼

Yes, architectural review applies to both library and application Kotlin modules. It evaluates module boundaries and dependency direction across different module types, verifying DI lifecycles and providing non-regression checks to ensure architectural consistency throughout the entire multi-module project.

What's the best way to enforce architecture consistency when refactoring Kotlin code?▼

The best way to enforce architecture consistency is by applying structured guardrails and non-regression checks during refactoring. This approach analyzes dependency direction and DI scopes, offering actionable remediation guidance to prevent architectural drift when changes touch multiple layers.