10-of-my-most-popular-text-to-image-series-prompts-78b0897e
generate a bunch of images, then you curate the results to handpick the best ones
Build, run, and test code projects for Rust, Go, and Java. Automatically detect project type, run unit tests if available, and report build status. Use after code changes to verify that project builds successfully, unit tests pass if they exist, and application runs without errors. Communicate results back to the requesting agent for fixing and re-testing.
Follow the repository instructions for this skill and your agent. Review the files and dependencies before adding it to your workflow.
SkillHub CLI
skillhub install frhn9/code-testerInspect the source and compatibility requirements, then follow its installation steps.
Give your agent the source link and ask it to inspect instructions and dependencies before explaining the installation steps.
Test code projects to verify builds and tests pass.
When asked to test changes:
Detect project type in specified directory:
Cargo.toml + src/ directorygo.mod, go.sum, or main.go
pom.xml or build.gradle / build.gradle.kts
Run tests (only if tests exist):
Build the project:
Report results:
When testing for another agent:
Format your report like:
Testing: <directory>
Project type: <rust|go|java>
Detected tests: <yes|no>
=== Results ===
✓ Tests: <passed/skipped/failed>
✓/✗ Build: <passed/failed>
<Relevant error messages if any>
If everything passes:
If something fails:
Execute the test script:
/root/.openclaw/workspace/skills/code-tester/scripts/test.sh <directory>
The script will:
cargo test → cargo build
go test ./... → go build
mvn test → mvn compile
./gradlew test → ./gradlew build -x test
Always run from the project directory. The script handles detection automatically.
These signals come from indexed source analysis and may lag behind changes. Check the current source files.
# Code Tester Test code projects to verify builds and tests pass. ## Workflow When asked to test changes: 1. **Detect project type** in specified directory: - Rust: `Cargo.toml` + `src/` directory - Go: `go.mod`, `go.sum`, or `main.go` - Java: `pom.xml` or `build.gradle` / `build.gradle.kts` 2. **Run tests** (only if tests exist): - Skip if no tests found - Run project-specific test commands - Capture test results 3. **Build the project**: - Run build commands - Capture build output and errors 4. **Report results**: - Clear summary of what happened - Test results (if run) - Build status - Any errors encountered ## Communication Protocol When testing for another agent: **Format your report like:** ``` Testing: <directory> Project type: <rust|go|java> Detected tests: <yes|no> === Results === ✓ Tests: <passed/skipped/failed> ✓/✗ Build: <passed/failed> <Relevant error messages if any> ``` **If everything passes:** - Report success clearly - Provide next steps if needed **If something fails:** - Report what failed (tests or build) - Include error logs - Suggest what to fix ## Running Tests Execute the test script: ```bash /root/.openclaw/workspace/skills/code-tester/scripts/test.sh <directory> ``` The script will: - Auto-detect project type - Run tests (if available) - Build the project - Return exit code 0 on success, 1 on failure ## Testing Strategy - **Rust**: `cargo test` → `cargo build` - **Go**: `go test ./...` → `go build` - **Java Maven**: `mvn test` → `mvn compile` - **Java Gradle**: `./gradlew test` → `./gradlew build -x test` Always run from the project directory. The script handles detection automatically.
generate a bunch of images, then you curate the results to handpick the best ones
generate a bunch of images, then you curate the results to handpick the best ones
Productivity system based on Maya calendar with 13 natural tones for project management and personal development
Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or multi-account), or reading/injecting/running secrets via op.