用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/tomevault-io/skills-registry --skill kt命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | kt |
| description | Build, test, analyze, or start Docker for a Kotlin project Use when this capability is needed. |
| metadata | {"author":"ajvelo"} |
Arguments: $ARGUMENTS
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:
export JAVA_HOME=$(/usr/libexec/java_home -v {version})
buildcd {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# 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.
analyzeDetekt (common):
cd {repo-path} && ./gradlew detekt
cd {repo-path} && ./gradlew :{module}:detekt
cd {repo-path} && ./gradlew detekt --auto-correct
ktlint (alternative):
cd {repo-path} && ./gradlew ktlintCheck
cd {repo-path} && ./gradlew ktlintFormat
Report issues with: rule name, file:line, message, severity.
dockerStarts the project's docker-compose.yml services (Postgres, Redis, any
stub/mock servers):
# 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:
docker compose -f {repo-path}/docker-compose.yml ps
If any container is unhealthy:
docker compose logs --tail=20 {service}
Common fixes:
docker ps to find the claimantdocker compose down -v && docker compose up -ddocker)cd to the resolved project pathSource: ajvelo/claude-toolkit — distributed by TomeVault.