Spine Event Engine
Official@spineeventengine · Portugal
Microservices & reactive DDD SDK for modern web
Agent Skills by Spine Event Engine
Showing 15 vetted skills indexed across 2 GitHub repositories.
SpineEventEnginegradle-review
Review Gradle build logic diffs for Spine conventions and best practices.
SpineEventEnginejava-to-kotlin
Convert Java source code into idiomatic Kotlin with preserved behavior and API semantics.
SpineEventEnginereview-docs
Reviews Kotlin/Java KDoc, Javadoc, and Markdown changes against Spine documentation conventions.
SpineEventEngineversion-bumped
Checks that the current Git branch's Gradle publishing version is strictly greater than the base ref.
SpineEventEnginecheck-links
Validate Hugo documentation links by rendering the site and scanning HTML with Lychee.
SpineEventEnginepre-pr
Run repository pre-pull-request version, build, and reviewer checks.
SpineEventEngineupdate-copyright
Update existing copyright headers in tracked source files using IntelliJ IDEA profiles.
SpineEventEnginebump-gradle
Update a repository's Gradle wrapper using official release notes and validate with a clean build.
SpineEventEnginedependency-audit
Audit buildSrc dependency declarations for version downgrades, BOM mismatches, and convention drift.
SpineEventEnginewriter
Write and revise Markdown and KDoc documentation with navigation sync.
SpineEventEnginekotlin-review
Review staged Kotlin and Java changes against repository coding guidelines and testing policy.
SpineEventEnginedependency-update
Update Gradle dependency version constants in Kotlin objects and generate a Markdown report.
SpineEventEngineapi-discovery
Resolve Maven artifact source paths for direct API inspection.
SpineEventEnginemove-files
Moves or renames git-tracked files and directories while preserving history and updating references.
SpineEventEnginebump-version
Update Spine project versions in version.gradle.kts and commit under strict rules.
Frequently Asked Questions About Spine Event Engine
FAQPage SchemaWhat specific tasks can developers perform using Spine Event Engine?▼
Developers can perform automated Java-to-Kotlin source migration, validate Gradle build logic against project conventions, audit dependency version drift, and synchronize documentation links. These capabilities ensure consistent code quality and build integrity across large-scale JVM microservices repositories.
Which engineering personas benefit most from these capabilities?▼
Platform engineers, build maintainers, and backend developers working within JVM ecosystems benefit most. These capabilities are designed for teams managing complex microservices who require strict adherence to coding standards, documentation accuracy, and reliable dependency versioning across multiple repositories.
What are the prerequisites for implementing these build-time checks?▼
Implementation requires a Gradle-based project structure and a Git-tracked repository. Users must have an environment configured for JVM development, as these utilities rely on Gradle build logic, IntelliJ IDEA profiles, and standard Git operations to execute migration and validation tasks.