kt
- Repo stars 0
- Author repo skills-registry
- Domain
- DevOps
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @tomevault-io · no license declared
- Token usage
- Lean
- Setup complexity
- Manual integration
- External API key
- Not required
- Operating systems
- Docker
- Runtime requirements
- Docker
- Detected file/system behavior
-
- Read-only
- Shell exec
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
## Kotlin build / test / analyze / docker
**Arguments:** $ARGUMENTS
## Project paths & JDK
Resolve project paths from `~/.claude/project-repos.json`. A Kotlin project
is any registry entry whose root contains `build.gradle` or `build.gradle.kts`.
JDK version is per-project and should be declared in the project's
`projects/{shortname}.md`. Set it before invoking Gradle:
```bash
export JAVA_HOME=$(/usr/libexec/java_home -v {version})
```
## Actions
### `build`
```bash
cd {repo-path} && ./gradlew build -x test
# Multi-module projects:
cd {repo-path} && ./gradlew :{module}:build -x test
```
On failure, suggest `./gradlew --refresh-dependencies` for dependency
errors. For compilation errors, quote the file/line and the offending type.
### `test`
```bash
# All tests:
cd {repo-path} && ./gradlew test
# A specific module:
cd {repo-path} && ./gradlew :{module}:test
# A filter (uses JUnit's `--tests`):
cd {repo-path} && ./gradlew test --tests "{filter}"
# Module + filter:
cd {repo-path} && ./gradlew :{module}:test --tests "{filter}"
```
If the project uses TestContainers, ensure Docker is running first.
Report: total / passed / failed / skipped. For failures, show class,
method, assertion error, and the first few lines of stack trace.
### `analyze`
Detekt (common):
```bash
cd {repo-path} && ./gradlew detekt
cd {repo-path} && ./gradlew :{module}:detekt
cd {repo-path} && ./gradlew detekt --auto-correct
```
ktlint (alternative):
```bash
cd {repo-path} && ./gradlew ktlintCheck
cd {repo-path} && ./gradlew ktlintFormat
```
Report issues with: rule name, file:line, message, severity.
### `docker`
Starts the project's `docker-compose.yml` services (Postgres, Redis, any
stub/mock servers):
```bash
# All services:
cd {repo-path} && docker compose up -d
# Specific service:
cd {repo-path} && docker compose up -d {service}
```
After start, wait ~5s and check health:
```bash
docker compose -f {repo-path}/docker-compose.yml ps
```
If any container is unhealthy:
```bash
docker compose logs --tail=20 {service}
```
Common fixes:
- Port conflict: `docker ps` to find the claimant
- Stale volumes: `docker compose down -v && docker compose up -d`
## Process
1. Parse arguments: action, shortname, optional module/filter/flags
2. Set JDK (skip for `docker`)
3. `cd` to the resolved project path
4. Run the command
5. Report result
---
> Source: [ajvelo/claude-toolkit](https://github.com/ajvelo/claude-toolkit) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-22 -->
Sections and files
Listed in source order.
sections -> Kotlin build / test / analyze / docker → Project paths & JDK → Actions → build → test → analyze
terms -> Arguments · Resolve project paths from ~/.claude/project-repos.json. · JDK version is per-project and should be declared in the project's projects/{shortname}.md. · On failure, suggest ./gradlew --refresh-dependencies for dependency errors. · If the project uses TestContainers, ensure Docker is running first. · Report: total / passed / failed / skipped. · Report issues with: rule name, file:line, message, severity. · 1. Parse arguments: action, shortname, optional module/filter/flags 2.
files/cmd -> ~/.claude/project-repos.json · build.gradle · build.gradle.kts · projects/{shortname}.md · build · ./gradlew --refresh-dependencies · test · --tests
body sha256 -> 1bc801ccc39b
Kotlin build / test / analyze / docker
Arguments: $ARGUMENTS
Project paths & JDK
Resolve project paths from
~/.claude/project-repos.json. A Kotlin project is any registry entry whose root containsbuild.gradleorbuild.gradle.kts. JDK version is per-project and should be declared in the project'sprojects/{shortname}.md. Set it before invoking Gradle:build
On failure, suggest
./gradlew --refresh-dependenciesfor dependency errors. For compilation errors, quote the file/line and the offending type.test
If the project uses TestContainers, ensure Docker is running first. Report: total / passed / failed / skipped. For failures, show class, method, assertion error, and the first few lines of stack trace.
analyze
Detekt (common): ktlint (alternative): Report issues with: rule name, file:line, message, severity.