ericrisco/rsc-harness / skills/java
java
VerifiedUse when writing, reviewing or refactoring modern Java (21+, 25 LTS) — records and sealed interfaces as algebraic data types, exhaustive pattern-matching switch over instanceof ladders, virtual-thread concurrency, structured concurrency and ScopedValue replacing ThreadLocal, Stream and Optional pipelines, compact-constructor validation, parametrized JDBC, and the Maven/Gradle build surface. NOT Spring framework wiring (that is `spring-boot`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 17.9 KB |
| evals/README.md | markdown | 1.7 KB |
| evals/cases.yaml | config | 4.5 KB |
| references/builds.md | markdown | 5.0 KB |
| references/concurrency.md | markdown | 5.0 KB |
| references/streams.md | markdown | 4.0 KB |
| scripts/verify.shexecutable | script | 3.2 KB |
scripts/verify.sh
View on GitHub#!/usr/bin/env bash
#
# verify.sh - local quality gate for a Java project (compile + test).
#
# Usage:
# cd <your-project-root> # the directory containing pom.xml or build.gradle(.kts)
# ./verify.sh
#
# Detects Maven vs Gradle, prefers the project wrapper (./mvnw / ./gradlew), and runs the
# build's compile + test + verify (`mvn -q verify` or `gradle check`).
# Missing build tools are skipped with a yellow warning (not a failure); a real
# compile/test failure exits non-zero. Read-only: never mutates your source.
#
# Portability: runs on stock macOS bash 3.2 (no mapfile, no associative arrays,
# no unguarded array expansions under `set -u`).
set -euo pipefail
# Colors only when stdout is a TTY (keeps logs/CI output clean).
if [ -t 1 ]; then
YELLOW=$'\033[33m'; RED=$'\033[31m'; GREEN=$'\033[32m'; RESET=$'\033[0m'
else
YELLOW=''; RED=''; GREEN=''; RESET=''
fi
failed=0
have() { command -v "$1" >/dev/null 2>&1; }
warn() { printf '%s[skip]%s %s\n' "$YELLOW" "$RESET" "$*"; }
fail() { printf '%s[fail]%s %s\n' "$RED" "$RESET" "$*"; failed=1; }
ok() { printf '%s[ ok ]%s %s\n' "$GREEN" "$RESET" "$*"; }
info() { printf -- '----- %s\n' "$*"; }
# Detect the build system. Neither present is a usage error, not a check failure.
build="none"
if [ -f pom.xml ]; then
build="maven"
elif [ -f build.gradle ] || [ -f build.gradle.kts ]; then
build="gradle"
fi
if [ "$build" = "none" ]; then
printf '%serror:%s no pom.xml or build.gradle(.kts) in %s - cd into your project root first.\n' \
"$RED" "$RESET" "$(pwd)" >&2
exit 2
fi
# Optional JDK version hint: warn (do not fail) if the major version is below 21.
info "java -version"
if have java; then
# `java -version` writes to stderr; first line e.g. 'openjdk version "25.0.1" ...'
ver_line="$(java -version 2>&1 | head -n1 || true)"
major="$(printf '%s' "$ver_line" | sed -n 's/.*version "\([0-9]*\).*/\1/p')"
if [ -n "$major" ] && [ "$major" -lt 21 ] 2>/dev/null; then
warn "JDK major $major detected; this skill targets 21+ (Java 25 LTS). $ver_line"
else
ok "$ver_line"
fi
else
warn "java not found on PATH (is a JDK installed?)"
fi
case "$build" in
maven)
info "Maven verify (compile + test + verify)"
mvn_cmd=""
if [ -x ./mvnw ]; then
mvn_cmd="./mvnw"
elif have mvn; then
mvn_cmd="mvn"
fi
if [ -z "$mvn_cmd" ]; then
warn "no ./mvnw and no mvn on PATH; cannot build (https://maven.apache.org)"
else
if "$mvn_cmd" -q -DskipTests=false verify; then
ok "maven verify passed ($mvn_cmd)"
else
fail "maven verify failed ($mvn_cmd)"
fi
fi
;;
gradle)
info "Gradle check (compile + test)"
gradle_cmd=""
if [ -x ./gradlew ]; then
gradle_cmd="./gradlew"
elif have gradle; then
gradle_cmd="gradle"
fi
if [ -z "$gradle_cmd" ]; then
warn "no ./gradlew and no gradle on PATH; cannot build (https://gradle.org/install/)"
else
if "$gradle_cmd" check; then
ok "gradle check passed ($gradle_cmd)"
else
fail "gradle check failed ($gradle_cmd)"
fi
fi
;;
esac
echo
if [ "$failed" -ne 0 ]; then
printf '%sFAIL:%s one or more checks failed.\n' "$RED" "$RESET"
exit 1
fi
printf '%sPASS:%s all checks passed.\n' "$GREEN" "$RESET"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 117k | Updated | Claude CodeCodex | Verified | Install |