Automate development guidance creation for the lemline-runner ecosystem.
npx skills add https://github.com/lemline/lemline --skill runner-dev
Please help me install this Agent Skill. Skill: runner-dev Source: https://github.com/lemline/lemline/tree/main/.claude/skills/runner-dev Command: npx skills add https://github.com/lemline/lemline --skill runner-dev
The Lemline Runner Development Guide consolidates best practices and architectural patterns for building, configuring, and testing modular lemline-runner components, ensuring consistent contributor experiences across the project.
Clone the Lemline repository and start with the main runner and core modules. Then read the module READMEs (lemline-runner, lemline-runner-common) for setup, testing, and contribution guidelines. Run tests for a specific module, e.g., ./gradlew :lemline-runner-waits:test, and follow the CLI and documentation references to implement new features.
High-intent search queries and answers about installing and using this skill.
A modular Quarkus and Kotlin runner project separates core runner, runner-common, and feature modules. This structure enforces architecture boundaries and maintains consistent contributor workflows across the ecosystem.
Multi-database testing conventions for Kotlin and Quarkus applications require native SQL usage and adherence to repository documentation. Running module-specific Gradle tests validates components across different database environments.
To run tests for a specific Quarkus runner module, execute the Gradle command targeting that module, such as ./gradlew :lemline-runner-waits:test. This isolates module testing and validates feature components independently within the project structure.
Use outbox and cleaner patterns in Kotlin development when managing modular runner infrastructure and feature modules. These patterns are required by the project structure to handle data consistency and maintain architecture standards across components.
The Lemline runner development guide supports onboarding new contributors by explaining module boundaries, repository standards, and common workflows. It consolidates architectural patterns to help contributors understand the modular Kotlin and Quarkus project structure.
lemlineGuide Kotlin development for the lemline-core workflow execution engine.
proto-at-blockExecute and debug JVM unit and integration tests across Gradle modules.
arbisoftImplement clean-architecture module boundaries and dependency rules in Android apps.
TymorIbrahimAutomate test-driven development for Quarkus 3.x applications with JUnit 5, Mockito, and JaCoCo.
