adambien/continuous-testing
bce/continuous-testing/SKILL.md
Continuous test-driven development loop — after every code change, builds the project, starts the server, and runs Unit Tests, Integration Tests, and System Tests. Applies on top of microprofile-server skill. Use during development when you want full verification after each change. Triggers on "continuous testing", "continuous-testing", "test loop", "st-loop", or requests to run all tests after every change.
$ install --global
skillsauthnpx skillsauth add adambien/airails continuous-testingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 30, 2026, 11:06 AM55.8s2 files scanned
SKILL.md
- name:
- continuous-testing
- description:
- Continuous test-driven development loop — after every code change, builds the project, starts the server, and runs Unit Tests, Integration Tests, and System Tests. Applies on top of microprofile-server skill. Use during development when you want full verification after each change. Triggers on "continuous testing", "continuous-testing", "test loop", "st-loop", or requests to run all tests after every change.
Continuous test-driven development loop using $ARGUMENTS. Apply all rules from /microprofile-server, plus the verification loop below.
Server Lifecycle
- start Quarkus in dev mode (
mvn quarkus:dev) once at the beginning of the session - keep the server running across changes — Quarkus dev mode handles live reload automatically
- only restart the server on major errors (e.g., server crash, port conflict, unrecoverable startup failure)
- do not stop and restart the server between changes
Verification Loop
After every code change, execute the following steps in order:
- Build & Unit Tests — run
mvn testin the service module to compile and execute unit tests - Integration Tests — run
mvn verifyin the service module to execute integration tests (failsafe plugin) - System Tests — before running, verify that the
-stmodule'spom.xmlincludes themaven-failsafe-pluginconfiguration. Then runmvn verifyin the-stmodule against the running server (already running in dev mode)
Rules
- do not skip any step — every change triggers the full loop
- if unit tests fail, stop and fix before proceeding to integration tests
- if integration tests fail, stop and fix before proceeding to system tests
- if system tests fail, stop and fix before continuing with the next change
- report the outcome of each step before proceeding to the next
- treat compilation errors as a failed step — fix before continuing
- keep the loop running until all steps pass or the user intervenes
Related Skills
adambien/java-conventions
tools
VerifiedTrustedCommunity
Generic, composable Java 25 code conventions — modern syntax, code style, naming, visibility, structure, methods, streams, exceptions, and documentation rules that apply across all Java contexts (single-file scripts, CLI apps, MicroProfile/Jakarta EE servers, libraries). Technology-neutral within the Java world; meant to be composed with context-specific skills (e.g. `java-cli-script`, `java-cli-app`, `microprofile-server`, `bce`). Use when writing, generating, or reviewing Java code anywhere the composed skill does not already specify style. Triggers on "Java conventions", "Java style", "Java code style", "modern Java", "Java 25", "idiomatic Java", or any request to write or review Java code where context-specific skills do not already cover style.
23SKILL.mdUpdated May 25, 2026
adambien/microprofile-server
development
VerifiedTrustedCommunity
Architecture and coding rules for long-running Java MicroProfile / Jakarta EE server applications — BCE layering, business components (BC), JAX-RS resources, CDI, JSON-P, testing (unit/integration/system), and Maven project structure. Use when creating, generating, scaffolding, writing, or reviewing code, resources, entities, boundaries, or business components in MicroProfile server projects. Not for serverless deployments.
23SKILL.mdUpdated Mar 27, 2026
adambien/java-cli-app
tools
VerifiedTrustedCommunity
Create and maintain multi-file Java 25 CLI applications packaged as executable JARs with zb (Zero Dependencies Builder). Use when asked to create a Java CLI application, a CLI project with multiple source files, or an executable JAR. Triggers on "Java CLI app", "CLI application", "multi-file Java", "executable JAR", "zb build", or requests for Java programs that need multiple source files or JAR packaging. Not for single-file scripts — use java-cli-script for those.
23SKILL.mdUpdated Mar 27, 2026
adambien/zb-release-pipeline
development
VerifiedTrustedCommunity
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb project", "add a zb release pipeline", "create a build workflow", "automate the zb build/release", or when a project has a .zb config and needs continuous builds/releases. Trigger even if the user doesn't say "zb" explicitly, as long as the project is a zb project (a .zb file is present and there is no Maven/Gradle build).
22SKILL.mdUpdated May 21, 2026